Can anyone out there help me? It sounds like if we switch to Subversion and we want to keep integration with Eclipse, we'll have to move our dependency info from ant scripts to Subversion externals properties. I'd really like to use Subversion but I don't think I can justify that sort of change to my team.
Meme Bag <memebag@yahoo.com> wrote:What I'm trying to do:
I'm trying to see how we can convert from our current SourceSafe version control system to Subversion. We develop many different products and need each Eclipse project to bind to multiple points in a common version control hierarchy.
Currently each project has a "build" folder in source control that contains the ant scripts to build the project. Those ant scripts create directories for source, test source, resources, etc., when they run and fetch the files needed for a specific project. We run that in the root of an empty Eclipse project and then bind the folders it created to different folders in SourceSafe.
Questions:
When you say "use the svn:externals property within that project", I assume you mean a folder in Subversion (since I can't set a Subversion property on an Eclipse project). Does this mean that every Eclipse project will have to have its own folder in Subversion? And does it imply that ant will stop defining which files go into a project and Subversion will take over that responsibility via the externals property?
When Subversion uses the svn:externals property to pull other items from the repository, does Subclipse know that the other items are under version control in Subversion? The documentation isn't clear about that.
---------------------------------
Yahoo! Messenger
Show us what our next emoticon should look like. Join the fun.
Received on Tue Apr 5 01:10:20 2005