Am Donnerstag, 21. Juni 2007 schrieb Philipp Bracher: [...] > 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".
I reconsider and packages is better than distributions as we do not distribute these packages 8)... > 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? Uh, in the case of magnolia-customexperimental (as package name) I would link to the custom-experimental branches in magnolia and dms. I think creating tags for each package which is a regular build (non experimental branch) is a good idea. O. ---------------------------------------------------------------- for list details see http://documentation.magnolia.info/docs/en/editor/stayupdated.html ----------------------------------------------------------------
