You may assign svn:externals property on root folder of your working
copy, eg.
svn:externals value:
core https://localhost:8443/svn/appfuseproject-core/trunk
web https://localhost:8443/svn/appfuseproject-web/trunk
so your svn repo structure will look like:
(you have to create 2 repos for web, core modules)
root/
appfuseproject/
trunk/
bin/
src/
core/ <only empty folder here - pointing to external repo location>
web/ <only empty folder here - pointing to external repo location>
README.txt
pom.xml
branches
tags
appfuseproject-core/
trunk/
<contents-of-core-module-here>
branches
tags
appfuseproject-web/
trunk/
<contents-of-core-module-here>
branches
tags
Personally I like to have only one repo per appfuse modular (generally
maven modular) project with nested structure (trunk, branches, tags) for
each module - in separate subfolder named 'projectname-modulename' +
svn:externals propeties pointing to those locations set on parent module.
kbighorse wrote:
Right now, I have in my repository:
root/
appfuseproject/
trunk/
bin/
src/
core/
web/
README.txt
pom.xml
branches
tags
This seems wrong, since I want to also be able to check out the sub-modules
as projects in their own right. Or is this right, and I should also have
trunk/branches/tags set up in core and web? I'm new to Subversion and just
want to know how people have their repositories and Eclipse dev environments
set up. Thanks so much!
Kimball
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@appfuse.dev.java.net
For additional commands, e-mail: users-h...@appfuse.dev.java.net
