[
http://jira.codehaus.org/browse/MEAR-64?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95680
]
Stephane Nicoll commented on MEAR-64:
-------------------------------------
come on :) Can't you see?
You have a jar with dependency com.computas.mt:mt-jar and an EJB with
dependency com.computas.mt:mt-jar
This is a clash names problem. I recommend you to update the artifactId of
those two modules.
Note also that the following is completely useless
{code:xml}
<jarModule>
<groupId>com.computas.mt</groupId>
<artifactId>mt-xml-schema</artifactId>
</jarModule>
{code}
modules configuration should only be used if you want to customize something.
If the defaut values are used, you don't need to include it there.
> Transitive dependency artifacts cannot be exploded
> --------------------------------------------------
>
> Key: MEAR-64
> URL: http://jira.codehaus.org/browse/MEAR-64
> Project: Maven 2.x Ear Plugin
> Issue Type: Bug
> Affects Versions: 2.3
> Reporter: Harald Soevik
> Priority: Minor
>
> I cannot find a way to explode an artifact when a project is directly
> dependent on artifact B and transitively dependent on A.
> Either A cannot be exploded because it is not defined as direct dependency,
> or A cannot be included as transitive dependency because it has already been
> exploded as a direct dependency.
> Might be worth a fix ?
--
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
