On 12/23/05, Patrick O'shea <[EMAIL PROTECTED]> wrote: > > > Hi, > > Should i be able to do a release:prepare from a parent project ?
Yes, parent and sub projects must be in snapshot state. If the parent project does not have a snapshot version number, then it will > fail. > But if the parent has a snapshot number then it will fail when it runs the > release:prepare > at the child project because it can't release due to a non released > parent. When performing release:prepare in a sub project, the parent cannot be in snapshot state. The key here is that we want to be able to reproduce the build with a label. Any snapshot state from parent or dependencies will prevent that from happening. > thanks > patrick > > > > > > > > > *dan tran <[EMAIL PROTECTED]>* > > 12/22/2005 08:52 PM Please respond to > "Maven Users List" <users@maven.apache.org> > > To > Maven Users List <users@maven.apache.org> cc > Subject > Re: [m2]release:prepare requires snapshots ? > > > > > It follows maven development process where > > - during development, every one works on snapshots > > - at release time, the snapshost got changed to release version, check > back into SCM, label, and build. > This is where customer can use, including qa, stake holder, etc > > - then the version is increamented with snapshot and check into SCM > again. > > -Dan > > > On 12/22/05, Patrick O'shea <[EMAIL PROTECTED]> wrote: > > > > > > Hi, > > > > I'm am trying to use the release:prepare goal. > > I can see from the source code that it is supposed to throw an > exception > > if the project being release is not a snapshot. > > Why is this ? > > > > > > Kind regards, > > Patrick O'Shea > > > > > > > > > > > >
