In a project with war packaging when I add a dependency to the release plugin
<plugin>
<artifactId>maven-release-plugin</artifactId>
<configuration>
<preparationGoals>clean install</preparationGoals>
</configuration>
</plugin>
I get the following output:
INFO] --- maven-install-plugin:2.3:install (default-install) @ webapp-os ---
INFO] Installing C:\project\target\webapp-os-4.4.2.jar to
C:\devel\maven\repository\<groupid>....\webapp-os\4.4.2\webapp-os-4.4.2.war
^
^
removing the dependency to the release plugin I get the correct behaviour
[INFO] --- maven-install-plugin:2.3:install (default-install) @ webapp-os ---
[INFO] Installing C:\project\webapp-os\target\webapp-os-4.4.2.war to
C:\devel\maven\repository\<groupid>....\webapp-os\4.4.2\webapp-os-4.4.2.war
this is the same running maven 2.2.1 or 3.0-alpha-7
Why would the install plugin ever copy a jar file to a war file?
and why can the dependency to the release plugin mess up running mvn
clean install?
what puzzles me even more is that when looking at the effective pom
the project I was running mvn clean install on already inherits the
same dependency to the release plugin from its parent.
Raphael
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
