Do you have a similar setup or do you checkout the content of
trunk and the
modules in one working copy?
This is what I do. In certain cases we do have a shell script in svn
which does the job.
As far as I know it's not yet possible to create a "symbolic link"
in svn
in module dms which links to pom.xml in trunk. Right?
Not really.
One more question and some thoughts related to svn and project
setup...
Checkout in one working copy doesn't work for me the way I tried
(can't find
the description anymore...).
I created a custom-experimental branch also for magnolia-module-dms.
It would be nice to checkout from one source to get a complete
custom-experimental project created from multiple sources like
described
in "Chapter 3. Advanced Topics: Externals Definitions"
(http://svnbook.red-bean.com/nightly/en/svn.advanced.externals.html).
We do not use externals because you have to change them when you do
releases of independent modules (like dms). Sometime I prefer to use
maven to install the right versions (incl. sources). Often you don't
won't to change all the modules at once.
But where to create the directory with externals definition in svn?
I propose /magnolia/packages
What about a "package" directory in the top level?
We could provide different "packages", "flavours", "distributions":
magnolia-customexperimental
magnolia-full
magnolia-webapp
magnolia-webapp-with-samples
I think "distributions" fits best as term and directory name followed
by "flavours".
We can try that to see how it works in daly live, but to which dms
would you link? to trunk? What when you like to checkout magnolia
3.0.2 with the correct dms version. Do we create tags for each package?
Philipp Bracher
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
