[MWAR-59] artifact extension set incorrectly in a multi-module build

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0, 2.0.1
• Fix Version/s: 2.0.2
• Assignee: Ernesto S. Tolentino Jr.
• Reporter: Brett Porter
• Created: 07/Jul/06 01:10
• Updated: 05/Nov/06 21:09
• Resolved: 05/Nov/06 12:24

Description

from the list...

unfortunately MWAR-38 is not fully fixed - It still does not work in a
multi-module build.
We do have here the following structure:

root
jarmodule
ejb
webapp

Running a "mvn package" inside the webapp module, the EJB-Client jar from
the ejb module is resolved correctly and copied to WEB-INF/lib with the
correct ".jar" ending.
Running the "mvn package" from the root module, the ejb-client jar from the
ejb module is resolved but copied with a ".ejb-client" ending, and not with
".jar".
You can test this by using the "daytrader" example from the Maven book.