[ http://jira.codehaus.org/browse/MWAR-7?page=comments#action_61593 ]
Brian Fox commented on MWAR-7:
------------------------------
I can try to create one, but I'm leaving for a trip today. In general the
project needs to look like this:
Parent
Project A (Jar)
Project B (War)
When you run from Project B (assuming A is already installed) you get
projecta-1.0.jar, if you run from the parent, you get projecta.jar.
> Referenced projects' artifacts naming scheme behaves differently when ran
> from reactor
> --------------------------------------------------------------------------------------
>
> Key: MWAR-7
> URL: http://jira.codehaus.org/browse/MWAR-7
> Project: Maven 2.x War Plugin
> Type: Bug
> Environment: maven-war-plugin versions 2.0-beta-1 and 2.0-beta-2
> Reporter: Cédric Vidal
> Assignee: Maria Odea Ching
> Fix For: 2.0
>
>
> When running mvn install from a war packaged project, the referenced
> projects' artifacts are bundled into the WEB-INF/lib directory with the
> following naming scheme ${groupId}-${artifactId}-${version}.jar, but when
> running mvn install as part of the reactor, the referenced projects'
> artifacts are bundled into the WEB-INF/lib directory with the following
> naming scheme ${pom.build.finalName}.jar
> The naming scheme should be the same in the two situations for the sake of
> consistency, but also to avoid the disturbing (for the end user) situation
> where you end up having the same dependencies present twice with different
> names.
--
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
