« Back to General Discussion

RE: Re: RE: Audium Studio 5 and subversion

Combination View Flat View Tree View
Threads [ Previous | Next ]
Audium Studio 5 and subversion
Answer
7/10/06 6:47 AM
There seems to reside a problem in Audium Studio 5 when dealing with subversion. When ever a change is made to an Audium project page, which has been checked out from subversion, the .svn subversion folder is deleted from the <project>/callflow/pages directory within the Audium project. From within Audium Studio 5 project I have set the Properties of the .svn folder to Read only and Derived, but this seems to have no bearing on preventing the deletion of the .svn folder. Any advice on this issue would be appreciated. [/img]
Flag

RE: Audium Studio 5 and subversion
Answer
7/11/06 7:31 PM as a reply to Anonymous.
Hi Adrian,

While we have not tested Audium Studio with subversion, Studio should work with any source control software. We will look into the behavior you described and post our results.

Regards,
Michael
Flag

RE: Audium Studio 5 and subversion
Answer
7/11/06 9:14 PM as a reply to Anonymous.
Hi Adrian,

Could you explain how do you use Subversion with Audium Studio? Do you use Eclipse plugin? If so, which one?

Note that source control integration is handled by Eclipse, not Audium Studio directly. CVS plugin for Eclipse, for example, monitors CVS specific files and does not allow to remove them from the project folder. The same behavior should apply to SVN, hence if you could provide us with details on your integration with SNV, it would help us to investigate the issue you are seeing.

Regards,
Michael
Flag

RE: Audium Studio 5 and subversion
Answer
6/11/08 10:47 PM as a reply to Anonymous.
I've also encountered this problem. I do not have Subversion integrated with Eclipse but will investigate that option.

At the moment, I perform code management external to Eclipse/Audium and import the files as needed. With ClearCase there didn't seem to be an issue since, unless checked out, all files are flagged read-only.

With Subversion, the typical policy is to check-out the tree and perform updates to commit changes back into the repository. Subversion uses hidden .svn directories to manage versioning of the directory contents (similar to CVS) and when saving a change to the Audium application, the .svn under the pages directory is deleted.

My supposition is that since the .svn directory is not a page, the save is eliminating it from the tree. Perhaps the plug-in will resolve that issue. Either way, it is rare to change the content at the pages level and all directories above and below contain the .svn elements so recovery is relatively simple (much better than losing view.dat on a ClearCase snapshot view).
Flag

Re: RE: Audium Studio 5 and subversion
Answer
8/25/08 10:04 PM as a reply to Anonymous.
We seem to have worked through this issue by adding the Subclipse plug-in (http://subclipse.tigris.org/) to the Audium 5.2 environment. This stopped the behavior of the pages\.svn directory from getting blown away.

I had tried just adding the .svn to the team/Ignored Resources preference but that didn't help. It seems the Audium 5.2 plug-in really need Subclipse to ignore the directory.

Caveat, we aren't generally using Subclipse from within Audium as part of our processes. The directories remain checked out and we do commit/update from either the Tortise shell extension or from the svn command line in a dos window. As such, I can't promise what will happen if you use Subversion via the Subclipse console.
Flag

Re: RE: Audium Studio 5 and subversion
Answer
9/10/08 2:42 AM as a reply to Anonymous.
What version of Subclipse are you using? I wanted to try it with Studio 5.2, but the latest versions of Subclipse aren't compatible with the version of Eclipse that Studio uses (3.1).
Flag

RE: Re: RE: Audium Studio 5 and subversion
Answer
1/15/10 10:41 PM as a reply to Ken Stoll.
An update: Further research indicated that even with the subclipse plug-in, we still had issues when using "Import as an Audium project".  Apparently this form of import would review the call flow and elminiate any subdirectories of the pages folder that were not defined in the application, specifically the .svn directory.
 
The proper work around seems to be as follows:
1. Define *.svn in Eclipse properties under Team | Ignored Resources
2. When importing an Audium project, use the 'Existing Projects into Workspace' source instead of the 'Existing Audium Project into Workspace'.
 
So far these have worked for us.
 
 
Flag