We'll be working more on multiproject releases shortly. It's a thorn in our own side come release time :)
- Brett On 7/12/05, Emmanuel Venisse <[EMAIL PROTECTED]> wrote: > > > Wilfred Springer wrote: > > All, > > > > I'm trying to get the maven release plug-in working. My project > > organization looks like this: > > > > /bignumbers/bignumbers-core > > /bignumbers-parser > > /bignumbers-interpreter > > > > Every directory mentioned above has its own pom.xml file. All > > subdirectories refer to the pom from the /bignumbers directory as their > > parent. > > > > Other dependencies: > > bignumbers-interpreter -> bignumbers-core > > bignumbers-interpreter -> bignumbers-parser > > > > Now the problem seems to be that m2 release:prepare fails since there > > are dependencies on snapshot artifacts. > > yes, we don't allow snapshot version for a release for obtain > reproductible build from tag versions. > > > > > If I go to the root of this project, then m2 release:prepare results in > > the files in /bignumbers directory being tagged. Then the build breaks, > > since it notices that the parent of bignumbers-core hasn't been released > > yet. > > > > I don't get it....... > > > > you need to install/deploy the parent before release sub-components. > you can run "m2 release:prepare release:perform" in your root directory > for check/tag/deploy your components. > > if you want to run it in multiple step, you must run this: > -in the root directory: m2 -N release:prepare release:perform => > release only the root pom > in other subprojects : m2 release:prepare release:perform > > Emmanuel > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
