Reactor builds actually works in M3, so I'm not surprised.
/Anders (mobile) Den 26 dec 2010 15.39 skrev "Benson Margulies" <[email protected]>: > The interesting thing is that M3 gets this right. > > On Sat, Dec 25, 2010 at 11:12 PM, Marshall Schor <[email protected]> wrote: >> The normal preparation goals for release:prepare stop short of "install" - they >> are: clean verify. Verify is one before install. You can find this information >> out by looking in the maven-release-plugin source, in the class PrepareReleaseMojo. >> >> I don't know the reason for this choice, but it would seem to me it may be >> perhaps rooted in a desire to have the "release:perform" step do a build from a >> checkout of the tag from SVN and not be dependent on anything (at that version) >> previously installed into the local repo. >> >> -Marshall Schor >> >> On 12/24/2010 8:07 PM, Benson Margulies wrote: >>> On Thu, Dec 23, 2010 at 3:25 PM, Mark Struberg <[email protected]> wrote: >>>> Hi Benson! >>>> >>>> Please check the preparationGoals property in the release plugin [1] >>>> >>>> Maybe you Please try with something like -DpreparationGoals="clean install" >>> I used to have that incantation but eliminated it because I didn't know why. >>> >>> I guess now I do. >>> >>> Thanks. >>> >>> >>>> >>>> LieGrue, >>>> strub >>>> >>>> [1] http://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.html#preparationGoals >>>> >>>> >>>> --- On Thu, 12/23/10, Benson Margulies <[email protected]> wrote: >>>> >>>>> From: Benson Margulies <[email protected]> >>>>> Subject: release plugin versus dependency plugin >>>>> To: "Maven Users List" <[email protected]> >>>>> Date: Thursday, December 23, 2010, 6:17 PM >>>>> Under a single aggregate project, I >>>>> have two projects. >>>>> >>>>> Project 1 builds an extra artifact with a classifier. >>>>> >>>>> Project 2 uses dependency:unpack to unpack it for inclusion >>>>> in a, yes, >>>>> larger artifact. >>>>> >>>>> All's well until I try to run the release:prepare goal, at >>>>> which >>>>> point, the first artifact is missing when the second >>>>> project asks for >>>>> it. >>>>> >>>>> any ideas? Why is the :prepare run different? >>>>> >>>>> >>>>> [INFO] Embedded error: Unable to download the artifact from >>>>> any repository >>>>> [INFO] >>>>> [INFO] Try downloading the file manually from the project >>>>> website. >>>>> [INFO] >>>>> [INFO] Then, install it using the command: >>>>> [INFO] mvn install:install-file >>>>> -DgroupId=com.basistech.jug >>>>> -DartifactId=rlp-gate-plugin -Dversion=8 >>>>> -Dclassifier=gate-plugin >>>>> -Dpackaging=zip -Dfile=/path/to/file >>>>> [INFO] >>>>> [INFO] Alternatively, if you host your own repository you >>>>> can deploy >>>>> the file there: >>>>> [INFO] mvn deploy:deploy-file >>>>> -DgroupId=com.basistech.jug >>>>> -DartifactId=rlp-gate-plugin -Dversion=8 >>>>> -Dclassifier=gate-plugin >>>>> -Dpackaging=zip -Dfile=/path/to/file -Durl=[url] >>>>> -DrepositoryId=[id] >>>>> [INFO] >>>>> [INFO] >>>>> [INFO] com.basistech.jug:rlp-gate-plugin:zip:8 >>>>> >>>>> --------------------------------------------------------------------- >>>>> 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] >>>> >>>> >>> --------------------------------------------------------------------- >>> 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] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] >
