Changing goals during perform produce strange comportment
---------------------------------------------------------
Key: MRELEASE-578
URL: http://jira.codehaus.org/browse/MRELEASE-578
Project: Maven 2.x Release Plugin
Issue Type: Bug
Affects Versions: 2.0
Reporter: fabrice
Attachments: consoleText[1]
I have a Multi Module Maven project.
I personalise a profil especially for realising snapshots
Test14StandardModules
Test14standardmoduleear
Test14standardmodulewar
Test14StandardModuleBusiness
The ear -> war -> business
Each of them inherit from the Test14StandardModules
In the parent pom I have the profile bellow :
<profile>
<id>almerys-release-profile</id>
<build>
<plugins>
<plugin>
<inherited>true</inherited>
<artifactId>maven-release-plugin</artifactId>
<version>2.0</version>
<configuration>
<preparationGoals>clean
verify</preparationGoals>
<useReleaseProfile>false</useReleaseProfile>
<goals>antrun:run scm:checkin deploy
</goals>
<arguments>-Dmessage="Release.properties
autocommit" -Palmerys-release-profile</arguments>
</configuration>
</plugin>
<plugin>
<inherited>true</inherited>
<artifactId>maven-antrun-plugin</artifactId>
<version>1.3</version>
<configuration>
<tasks>
<echo>COPY
RELEASE.PROPERTIES</echo>
<copy
file="${WORKSPACE}/release.properties"
tofile="${WORKSPACE}/.release.properties-save" />
</tasks>
</configuration>
</plugin>
<plugin>
<inherited>true</inherited>
<artifactId>maven-scm-plugin</artifactId>
<version>1.3</version>
<configuration>
<includes>.release.properties-save</includes>
<connectionType>developerConnection</connectionType>
<workingDirectory>${WORKSPACE}</workingDirectory>
</configuration>
</plugin>
</plugins>
</build>
</profile>
I release with the command bellow :
-Dresume=false release:prepare release:perform -P almerys-release-profile -e
It failed because the business released jar is not found.
the console output is attached
When I change the goals perform antrun:run scm:checkin deploy to deploy
antrun:run scm:checkin it works.
It seems that the perform goal run the two first goals on each module and apply
the last only on the parent pom.
Strange ?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
