mvn install - multiple modules using subproject as launch point - pom.xml gets
renamed installed in local repository as a .war file
-----------------------------------------------------------------------------------------------------------------------------------
Key: MNG-1784
URL: http://jira.codehaus.org/browse/MNG-1784
Project: Maven 2
Type: Bug
Components: Reactor and workspace
Versions: 2.0
Reporter: David Boden
Attachments: demo.zip
Please unzip the attached demo.zip and navigate to the BigWAR directory. From
here, type:
mvn install
You'll get this logged:
[INFO] Installing C:\dev\demo\BigWAR\pom.xml to C:\Documents and
Settings\dboden\.m2\repository\com\demo\demo\BigWAR\SNAPSHOT\BigWAR-SNAPSHOT.war
The pom.xml gets renamed to a .war file and installed in the repository!
I admit that I've not quite used the pom.xml sub modules features as intended.
However, it would be better if we could use them in this way! Any pom.xml
should be able to specify that sub modules should be built beforehand. Why
should we have to use the parent as the starting point for a sub modules build?
In any case, I'm sure you'll agree that installing a .xml file as a .war is
incorrect behaviour, in any case.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
