I always use multi-module, but I always am working on J2EE apps. If you want common shared projects, then split this up, but you still might have multi-modules if you are creating j2ee apps.
On Thu, Jun 5, 2008 at 3:22 PM, Kent Närling <[EMAIL PROTECTED]> wrote: > 2008/6/6 Mick Knutson <[EMAIL PROTECTED]>: > > > dist is usually going to be an assembly, and you add assembly descriptors > > into src/assemble/*.xml > > You do not store the rpm's or bin's there. They do not end up in svn in > > other words. > > > > I have: > > root pom.xml > > |-->common 1..* jar's > > |-->core > > |-->src > > |-->assemble > > |-->main/resources > > |-->site > > |-->/xdoc/**.* (docs) > > |-->tools > > |-->webapps 1..* wars > > > > So common, core, tools, webapps etc would be modules of the main project? > So you all seem to recommend creating a module based layout? > > Maybe I expressed myself a bit unclear, I never meant that the dist > CONTAINED RPM:s or so! > I mean that it's CREATES RPM:s etc ;-) > > In a module based layout like this, what if I then want to work on a module > (ie a plugin etc) without having to checkout the main project? > Maybe I don't even have access to it? (only the jar:s) > > Also, what if we would like to release a separate version of a module > outside of a release? (ie a patch or a feature without having to do a > release cycle for the whole product) > I can only imagine that it will be a bit "messy" in SVN then? since the > modules won't have separate trunk:s and tag:s etc? or? > > > > > > On Thu, Jun 5, 2008 at 3:01 PM, Kent Närling <[EMAIL PROTECTED]> > > wrote: > > > > > Sorry, didn't get what you mean by that? > > > > > > You mean dist should not be a project on its own, or? > > > > > > > > > 2008/6/5 Mick Knutson <[EMAIL PROTECTED]>: > > > > > > > dist should be src/assemble for assemblies. > > > > > > > > On Thu, Jun 5, 2008 at 2:41 PM, Kent Närling < > [EMAIL PROTECTED] > > > > > > > wrote: > > > > > > > > > We have a project in SVN that is made of several projects, > something > > > like > > > > > this: > > > > > > > > > > - core - core project > > > > > - common - common libraries > > > > > - pluginA > > > > > - pluginB > > > > > ... etc > > > > > - doc - for documentation) > > > > > - tools - some command line tools > > > > > - dist - distribution project which packages all of the above > > projects > > > > into > > > > > one or more packages (RPM:s for instance) > > > > > > > > > > Most of the the projects generate jar:s, but some generate EAR:s. > > > > > > > > > > Now on one hand we could create a main project with modules, but > that > > > > ties > > > > > the modules so tightly to the main project, or? > > > > > And the plugins (and future plugins) we would like to be able to > give > > > to > > > > > third-party resources etc and they should not have access to most > > core > > > > > sources etc > > > > > Additionally, if we put modules in subdirectories in SVN (as > > > recommended) > > > > > it > > > > > becomes more awkward to release separate versions of the modules? > > > > > > > > > > At the end it should be easy to build the whole project and package > > it, > > > > for > > > > > instance automatically from within continuum for instance. > > > > > Additionally, for developers it should be easy to check out all > > > projects > > > > > automatically and recursively into Eclipse... > > > > > > > > > > Any suggestions about the best strategy for a project like this? > > > > > > > > > > //Kent > > > > > > > > > > > > > > > > > > > > > -- > > > > --- > > > > Thank You… > > > > > > > > Mick Knutson > > > > BASE Logic, inc. > > > > > > > > Website: http://baselogic.com > > > > Blog: http://baselogic.com/blog > > > > BLiNC Magazine: http://blincmagazine.com > > > > Linked IN: http://linkedin.com/in/mickknutson > > > > DJ Mick: http://djmick.com > > > > MySpace: http://myspace.com/mickknutson > > > > Tahoe: http://tahoe.baselogic.com > > > > > > > > > > > > > > > > -- > > > Kent Närling > > > > > > System Architect > > > SEAMLESS > > > Dalagatan 100, 8 tr, 113 43 Stockholm, Sweden > > > Phone: +46 8 5648 7800, fax: +46 8 5648 7823 > > > Mobile: +46 70 836 9925 > > > Mail: [EMAIL PROTECTED] > > > www.seamless.se > > > > > > > > > > > -- > > --- > > Thank You… > > > > Mick Knutson > > BASE Logic, inc. > > > > Website: http://baselogic.com > > Blog: http://baselogic.com/blog > > BLiNC Magazine: http://blincmagazine.com > > Linked IN: http://linkedin.com/in/mickknutson > > DJ Mick: http://djmick.com > > MySpace: http://myspace.com/mickknutson > > Tahoe: http://tahoe.baselogic.com > > > > > > -- > Kent Närling > > System Architect > SEAMLESS > Dalagatan 100, 8 tr, 113 43 Stockholm, Sweden > Phone: +46 8 5648 7800, fax: +46 8 5648 7823 > Mobile: +46 70 836 9925 > Mail: [EMAIL PROTECTED] > www.seamless.se > -- --- Thank You… Mick Knutson BASE Logic, inc. Website: http://baselogic.com Blog: http://baselogic.com/blog BLiNC Magazine: http://blincmagazine.com Linked IN: http://linkedin.com/in/mickknutson DJ Mick: http://djmick.com MySpace: http://myspace.com/mickknutson Tahoe: http://tahoe.baselogic.com
