You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Harald Soevik (JIRA)" <ji...@codehaus.org> on 2007/05/10 16:50:12 UTC
[jira] Created: (MEAR-64) Transitive dependency artifacts cannot be
exploded
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
Fix For: 2.4
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
[jira] Closed: (MEAR-64) Transitive dependency artifacts cannot be
exploded
Posted by "Stephane Nicoll (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEAR-64?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stephane Nicoll closed MEAR-64.
-------------------------------
Resolution: Cannot Reproduce
Duplicated artifact issue.
> 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
[jira] Issue Comment Edited: (MEAR-64) Transitive dependency
artifacts cannot be exploded
Posted by "Harald Soevik (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEAR-64?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95679 ]
Harald Soevik edited comment on MEAR-64 at 5/11/07 10:18 AM:
-------------------------------------------------------------
I've got one module that I want to explode: mt-jar.
{noformat}
<modules>
<ejbModule>
<groupId>com.computas.mt</groupId>
<artifactId>mt-jar</artifactId>
<unpack>true</unpack>
</ejbModule>
<jarModule>
<groupId>com.computas.mt</groupId>
<artifactId>mt-xml-schema</artifactId>
</jarModule>
...
</modules>
{noformat}
Then, mt-xml-schema has mt-jar as dependency (this is from mt-xml-schema's pom.xml):
{noformat}
<dependencies>
<dependency>
<groupId>com.computas.mt</groupId>
<artifactId>mt-jar</artifactId>
</dependency>
...
</dependencies>
{noformat}
Trying to build the EAR results in this output:
{noformat}
[INFO] [ear:ear]
...
[INFO] Copying artifact[ejb:com.computas.mt:mt-jar:1.0.8-SNAPSHOT] to[mt-jar-1.0.8-SNAPSHOT.jar] (unpacked)
[INFO] Expanding: /home/computas/.m2/repository/com/computas/mt/mt-jar/1.0.8-SNAPSHOT/mt-jar-1.0.8-SNAPSHOT.jar into /home/computas/matsys/mt-ear-clustered/target/mt-ear-clustered-1.0.8-SNAPSHOT/mt-jar-1.0.8-SNAPSHOT.jar
...
[INFO] Copying artifact[jar:com.computas.mt:mt-jar:1.0.8-SNAPSHOT] to[mt-jar-1.0.8-SNAPSHOT.jar]
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Error copying EAR modules
Embedded error: /home/computas/matsys/mt-ear-clustered/target/mt-ear-clustered-1.0.8-SNAPSHOT/mt-jar-1.0.8-SNAPSHOT.jar (Is a directory)
{noformat}
Observe that the mt-jar artifact is being copied twice, producing an error because it already exists as an exploded artifact.
was:
I've got one module that I want to explode: mt-jar.
{noformat}
<modules>
<ejbModule>
<groupId>com.computas.mt</groupId>
<artifactId>mt-jar</artifactId>
<unpack>true</unpack>
</ejbModule>
<jarModule>
<groupId>com.computas.mt</groupId>
<artifactId>mt-xml-schema</artifactId>
</jarModule>
...
</modules>
{noformat}
Then, mt-xml-schema has mt-jar as dependency:
{noformat}
<dependencies>
<dependency>
<groupId>com.computas.mt</groupId>
<artifactId>mt-jar</artifactId>
</dependency>
...
</dependencies>
{noformat}
Trying to build the EAR results in this output:
{noformat}
[INFO] [ear:ear]
...
[INFO] Copying artifact[ejb:com.computas.mt:mt-jar:1.0.8-SNAPSHOT] to[mt-jar-1.0.8-SNAPSHOT.jar] (unpacked)
[INFO] Expanding: /home/computas/.m2/repository/com/computas/mt/mt-jar/1.0.8-SNAPSHOT/mt-jar-1.0.8-SNAPSHOT.jar into /home/computas/matsys/mt-ear-clustered/target/mt-ear-clustered-1.0.8-SNAPSHOT/mt-jar-1.0.8-SNAPSHOT.jar
...
[INFO] Copying artifact[jar:com.computas.mt:mt-jar:1.0.8-SNAPSHOT] to[mt-jar-1.0.8-SNAPSHOT.jar]
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Error copying EAR modules
Embedded error: /home/computas/matsys/mt-ear-clustered/target/mt-ear-clustered-1.0.8-SNAPSHOT/mt-jar-1.0.8-SNAPSHOT.jar (Is a directory)
{noformat}
Observe that the mt-jar artifact is being copied twice, producing an error because it already exists as an exploded artifact.
> 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
[jira] Updated: (MEAR-64) Transitive dependency artifacts cannot be
exploded
Posted by "Stephane Nicoll (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEAR-64?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stephane Nicoll updated MEAR-64:
--------------------------------
Fix Version/s: (was: 2.4)
> 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
[jira] Commented: (MEAR-64) Transitive dependency artifacts cannot
be exploded
Posted by "Harald Soevik (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEAR-64?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95679 ]
Harald Soevik commented on MEAR-64:
-----------------------------------
I've got one module that I want to explode: mt-jar.
{noformat}
<modules>
<ejbModule>
<groupId>com.computas.mt</groupId>
<artifactId>mt-jar</artifactId>
<unpack>true</unpack>
</ejbModule>
<jarModule>
<groupId>com.computas.mt</groupId>
<artifactId>mt-xml-schema</artifactId>
</jarModule>
...
</modules>
{noformat}
Then, mt-xml-schema has mt-jar as dependency:
{noformat}
<dependencies>
<dependency>
<groupId>com.computas.mt</groupId>
<artifactId>mt-jar</artifactId>
</dependency>
...
</dependencies>
{noformat}
Trying to build the EAR results in this output:
{noformat}
[INFO] [ear:ear]
...
[INFO] Copying artifact[ejb:com.computas.mt:mt-jar:1.0.8-SNAPSHOT] to[mt-jar-1.0.8-SNAPSHOT.jar] (unpacked)
[INFO] Expanding: /home/computas/.m2/repository/com/computas/mt/mt-jar/1.0.8-SNAPSHOT/mt-jar-1.0.8-SNAPSHOT.jar into /home/computas/matsys/mt-ear-clustered/target/mt-ear-clustered-1.0.8-SNAPSHOT/mt-jar-1.0.8-SNAPSHOT.jar
...
[INFO] Copying artifact[jar:com.computas.mt:mt-jar:1.0.8-SNAPSHOT] to[mt-jar-1.0.8-SNAPSHOT.jar]
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Error copying EAR modules
Embedded error: /home/computas/matsys/mt-ear-clustered/target/mt-ear-clustered-1.0.8-SNAPSHOT/mt-jar-1.0.8-SNAPSHOT.jar (Is a directory)
{noformat}
Observe that the mt-jar artifact is being copied twice, producing an error because it already exists as an exploded artifact.
> 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
[jira] Commented: (MEAR-64) Transitive dependency artifacts cannot
be exploded
Posted by "Stephane Nicoll (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Commented: (MEAR-64) Transitive dependency artifacts cannot
be exploded
Posted by "Stephane Nicoll (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEAR-64?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95660 ]
Stephane Nicoll commented on MEAR-64:
-------------------------------------
I've already replied to this issue. Kinda weird, I can't find it back.
Transitive does not make any difference, just configure the module the usual way with exploded set to true.
{code:xml}
<modules>
<jarModule>
<groupId></groupId>
<artifactId></artifactId>
<exploded>true</exploded>
</jarModule>
[...]
</modules>
{code}
> 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