Re: Project structure and releasing

2006-06-30 Thread Andrew Williams
I may be wrong, but if your parent is, as in the book, a pom packaged artifact with a module list then doing a release at that level should prompt (with sensible defaults) the release of all the modules. Andy On Fri, 2006-06-30 at 21:29 +0200, Martijn Dashorst wrote: > All, > > I've updated the

Re: Project structure and releasing

2006-07-01 Thread Stefan Hübner
Andy, are you saying, that deploying the multiproject-pom as 1.2.1 would automatically update the submodule's dependency on their parent from 1.2-SNAPSHOT to 1.2.1? Is it even necessary to declare the parent's version the submodules refer to? -Stefan 2006/7/1, Andrew Williams <[EMAIL PROTECTED]

Re: Project structure and releasing

2006-07-01 Thread Andrew Williams
yes and yes. When running a release cycle a parent pom's upgrading version will be cascaded to the "parent" section of child modules, replacing the current version with the new one. It is currently necessary to specify the parent version in your child pom.xml, however, this will be removed in the

Re: Project structure and releasing

2006-07-01 Thread Barrie Treloar
of course in your parent pom.xml you can happily use ${project.version} to specify the dependencies on child modules which saves you worrying about that part :) I had problems with using ${project.version} as when the artifacts are deployed to a snapshot repository the pom metadata is using the

Re: Project structure and releasing

2006-07-01 Thread Andrew Williams
very good point, yes - it raises 2 questions 1) Do we need to start pushing the continuum heirarchy build idea faster? (trygvis, kenny and I had a brief talk about this yesterday) 2) should ${project.version} for SNAPSHOT perhaps insert SNAPSHOT rather than the dated stamp, perhaps providing ${pro

Re: Re: Project structure and releasing

2006-07-03 Thread Martijn Dashorst
Though I read on a separate thread on this list (http://www.nabble.com/Top-level-POM-behaviour-t1825699.html#a4980080) that doing a module based build is not working for separated projects. That is why I didn't put a modules section in the parent project. Here's the quote from Alexandre: be

Re: Re: Project structure and releasing

2006-07-03 Thread Barrie Treloar
On 7/3/06, Martijn Dashorst <[EMAIL PROTECTED]> wrote: Though I read on a separate thread on this list (http://www.nabble.com/Top-level-POM-behaviour-t1825699.html#a4980080) that doing a module based build is not working for separated projects. That is why I didn't put a modules section in the pa