Am Mittwoch, 13. Juni 2007 schrieb Oliver Lietz: > Am Mittwoch, 13. Juni 2007 schrieb Grégory Joseph: > > > We have a bi-directional dependency between Magnolia (a least when > > > doing a > > > complete webapp build) and DMS. > > > > Just don't ;) > > While we're on it, this is my directory setup (there is more which is not > relevant now): > > community > custom-experimental (branch) > magnolia (trunk) > > I modified the pom.xml from module dms in community to point (relativePath) > to the parent pom.xml in magnolia (trunk). > Do you have a similar setup or do you checkout the content of trunk and the > modules in one working copy? I'm not sure if this works, haven't tested it > but found a description for that. > 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?
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). But where to create the directory with externals definition in svn? 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". O. ---------------------------------------------------------------- for list details see http://documentation.magnolia.info/docs/en/editor/stayupdated.html ----------------------------------------------------------------
