You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jean Seurin (JIRA)" <ji...@codehaus.org> on 2010/01/19 10:09:55 UTC
[jira] Created: (MDEP-251) Artifacts qualifier are taken into
accounts correctly
Artifacts qualifier are taken into accounts correctly
-----------------------------------------------------
Key: MDEP-251
URL: http://jira.codehaus.org/browse/MDEP-251
Project: Maven 2.x Dependency Plugin
Issue Type: Bug
Affects Versions: 2.1
Environment: OSX 10.6.2, java 1.6.0_17
Reporter: Jean Seurin
Assignee: Brian Fox
Priority: Critical
I just introduced some qualifier for some libs that require to be compiled in java5.
I've been very confused when realizing that when packaging a webapp depending on those qualified artifacts, the non qualified versions are included instead.
It seems to come from dependency plugin.
Here is what happens:
When I do a dependency:tree on an artifact that depends directly on qualified libs, I get something regular:
[INFO] [dependency:tree {execution: default-cli}]
[INFO] org.company.project:stageof:jar:1.4-SNAPSHOT
[INFO] +- org.company.project:jar:jdk1.5:1.5-SNAPSHOT:compile
....
[INFO] +- org.company.commons:commons-xml:jar:jdk1.5:1.4-SNAPSHOT:compile
The stageof lib depends on the jdk1.5 qualified commons and commons-xml libs.
When I do a dependency:tree on an upper level webapp that depends on this stageof lib:
[INFO] org.company.project:webapp:war:1.13-SNAPSHOT
[INFO] +- org.company.project:stageof:jar:jdk1.5:1.4-SNAPSHOT:compile
[INFO] | +- org.company.commons:jar:1.4.0:compile
[INFO] | \- org.company.commons:commons-xml:jar:1.4-SNAPSHOT:compile
[INFO] +- org.company.commons:jar:jdk1.5:1.5-SNAPSHOT:compile
...
it finds correctly the qualified version of stageof, but include non qualified commons and commons-xml.
These unqualified versions are the dependencies of the also non qualified stageof-1.4-SNAPSHOT.
>From this behavior, I presume dependency plugin makes a mistake in looking from the wrong pom, probably not using the qualifier of the included dependency:
<dependency>
<groupId>org.company.project</groupId>
<artifactId>stageof</artifactId>
<version>1.4-SNAPSHOT</version>
<scope>compile</scope>
<classifier>jdk1.5</classifier>
</dependency>
Hope this is clear.
I could provide an example if you can't reproduce easily.
Actually, just adding a qualifier to the jar-plugin to produce the artifact and to the <dependency> section should do the job.
rgds,
jean
--
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: (MDEP-251) Artifacts qualifier are NOT taken into
accounts correctly
Posted by "Andreas Brieg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MDEP-251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=243725#action_243725 ]
Andreas Brieg commented on MDEP-251:
------------------------------------
@Joerg Schaible:
Looking at the attached test project I would expect that the maven dependency plugin tries to download {{some-zip-0.0.1-SNAPSHOT.zip}} and not {{some-zip-0.0.1-SNAPSHOT-x86.zip}} because this artifact does not specify a classifier.
Even if I add another profile with another classifier the dependency plugin will use the latest specified classifier for {{some-zip-0.0.1-SNAPSHOT.zip}}. So if using maven in a complex multi module project one would have to install/deploy all possible modules to the repository with every possible classifier. But that would just be redundant, because the majority of modules wouldn't have differences for different classifiers.
> Artifacts qualifier are NOT taken into accounts correctly
> ---------------------------------------------------------
>
> Key: MDEP-251
> URL: http://jira.codehaus.org/browse/MDEP-251
> Project: Maven 2.x Dependency Plugin
> Issue Type: Bug
> Affects Versions: 2.1
> Environment: OSX 10.6.2, java 1.6.0_17
> Reporter: Jean Seurin
> Assignee: Brian Fox
> Priority: Critical
> Attachments: test.maven-dependency-plugin.zip
>
>
> I just introduced some qualifier for some libs that require to be compiled in java5.
> I've been very confused when realizing that when packaging a webapp depending on those qualified artifacts, the non qualified versions are included instead.
> It seems to come from dependency plugin.
> Here is what happens:
> When I do a dependency:tree on an artifact that depends directly on qualified libs, I get something regular:
> [INFO] [dependency:tree {execution: default-cli}]
> [INFO] org.company.project:stageof:jar:1.4-SNAPSHOT
> [INFO] +- org.company.project:jar:jdk1.5:1.5-SNAPSHOT:compile
> ....
> [INFO] +- org.company.commons:commons-xml:jar:jdk1.5:1.4-SNAPSHOT:compile
> The stageof lib depends on the jdk1.5 qualified commons and commons-xml libs.
> When I do a dependency:tree on an upper level webapp that depends on this stageof lib:
> [INFO] org.company.project:webapp:war:1.13-SNAPSHOT
> [INFO] +- org.company.project:stageof:jar:jdk1.5:1.4-SNAPSHOT:compile
> [INFO] | +- org.company.commons:jar:1.4.0:compile
> [INFO] | \- org.company.commons:commons-xml:jar:1.4-SNAPSHOT:compile
> [INFO] +- org.company.commons:jar:jdk1.5:1.5-SNAPSHOT:compile
> ...
> it finds correctly the qualified version of stageof, but include non qualified commons and commons-xml.
> These unqualified versions are the dependencies of the also non qualified stageof-1.4-SNAPSHOT.
> From this behavior, I presume dependency plugin makes a mistake in looking from the wrong pom, probably not using the qualifier of the included dependency:
> <dependency>
> <groupId>org.company.project</groupId>
> <artifactId>stageof</artifactId>
> <version>1.4-SNAPSHOT</version>
> <scope>compile</scope>
> <classifier>jdk1.5</classifier>
> </dependency>
> Hope this is clear.
> I could provide an example if you can't reproduce easily.
> Actually, just adding a qualifier to the jar-plugin to produce the artifact and to the <dependency> section should do the job.
> rgds,
> jean
--
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: (MDEP-251) Artifacts qualifier are NOT
taken into accounts correctly
Posted by "Andreas Brieg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MDEP-251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=243721#action_243721 ]
Andreas Brieg edited comment on MDEP-251 at 11/19/10 3:04 AM:
--------------------------------------------------------------
I attached a file, which shows an incorrect behavior with classifiers. The project has a dependency on a zip file with no classifier. A second dependency is within a profile, which is active by default. The dependency in the profile uses a classifier. The maven dependency plugin tries to download the dependency, which is not in the profile, with the classifier of the dependency in the profile.
Please note that there must not exist any dependency listed in the project in your maven repositories in order to demonstrate the incorrect behavior.
was (Author: abr):
I attached a file, which shows an incorrect behavior with classifiers. The project has a dependency on a zip file with no classifier. A second dependency is within a profile, which is active by default. The dependency in the profile uses a classifier. The maven dependency plugin tries to download the dependency, which is not in the profile, with the classifier of the dependency in the profile.
Please note that there must not exists any dependencies listed in the project in your maven repositories in order to demonstrate the incorrect behavior.
> Artifacts qualifier are NOT taken into accounts correctly
> ---------------------------------------------------------
>
> Key: MDEP-251
> URL: http://jira.codehaus.org/browse/MDEP-251
> Project: Maven 2.x Dependency Plugin
> Issue Type: Bug
> Affects Versions: 2.1
> Environment: OSX 10.6.2, java 1.6.0_17
> Reporter: Jean Seurin
> Assignee: Brian Fox
> Priority: Critical
> Attachments: test.maven-dependency-plugin.zip
>
>
> I just introduced some qualifier for some libs that require to be compiled in java5.
> I've been very confused when realizing that when packaging a webapp depending on those qualified artifacts, the non qualified versions are included instead.
> It seems to come from dependency plugin.
> Here is what happens:
> When I do a dependency:tree on an artifact that depends directly on qualified libs, I get something regular:
> [INFO] [dependency:tree {execution: default-cli}]
> [INFO] org.company.project:stageof:jar:1.4-SNAPSHOT
> [INFO] +- org.company.project:jar:jdk1.5:1.5-SNAPSHOT:compile
> ....
> [INFO] +- org.company.commons:commons-xml:jar:jdk1.5:1.4-SNAPSHOT:compile
> The stageof lib depends on the jdk1.5 qualified commons and commons-xml libs.
> When I do a dependency:tree on an upper level webapp that depends on this stageof lib:
> [INFO] org.company.project:webapp:war:1.13-SNAPSHOT
> [INFO] +- org.company.project:stageof:jar:jdk1.5:1.4-SNAPSHOT:compile
> [INFO] | +- org.company.commons:jar:1.4.0:compile
> [INFO] | \- org.company.commons:commons-xml:jar:1.4-SNAPSHOT:compile
> [INFO] +- org.company.commons:jar:jdk1.5:1.5-SNAPSHOT:compile
> ...
> it finds correctly the qualified version of stageof, but include non qualified commons and commons-xml.
> These unqualified versions are the dependencies of the also non qualified stageof-1.4-SNAPSHOT.
> From this behavior, I presume dependency plugin makes a mistake in looking from the wrong pom, probably not using the qualifier of the included dependency:
> <dependency>
> <groupId>org.company.project</groupId>
> <artifactId>stageof</artifactId>
> <version>1.4-SNAPSHOT</version>
> <scope>compile</scope>
> <classifier>jdk1.5</classifier>
> </dependency>
> Hope this is clear.
> I could provide an example if you can't reproduce easily.
> Actually, just adding a qualifier to the jar-plugin to produce the artifact and to the <dependency> section should do the job.
> rgds,
> jean
--
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: (MDEP-251) Artifacts qualifier are taken into
accounts correctly
Posted by "Jean Seurin (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MDEP-251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=207424#action_207424 ]
Jean Seurin commented on MDEP-251:
----------------------------------
Sorry, made a mistake on the issue name itself. It should be:
Artifacts qualifier are NOT taken into accounts correctly
There don't seem to be a way to edit this Issue name.
> Artifacts qualifier are taken into accounts correctly
> -----------------------------------------------------
>
> Key: MDEP-251
> URL: http://jira.codehaus.org/browse/MDEP-251
> Project: Maven 2.x Dependency Plugin
> Issue Type: Bug
> Affects Versions: 2.1
> Environment: OSX 10.6.2, java 1.6.0_17
> Reporter: Jean Seurin
> Assignee: Brian Fox
> Priority: Critical
>
> I just introduced some qualifier for some libs that require to be compiled in java5.
> I've been very confused when realizing that when packaging a webapp depending on those qualified artifacts, the non qualified versions are included instead.
> It seems to come from dependency plugin.
> Here is what happens:
> When I do a dependency:tree on an artifact that depends directly on qualified libs, I get something regular:
> [INFO] [dependency:tree {execution: default-cli}]
> [INFO] org.company.project:stageof:jar:1.4-SNAPSHOT
> [INFO] +- org.company.project:jar:jdk1.5:1.5-SNAPSHOT:compile
> ....
> [INFO] +- org.company.commons:commons-xml:jar:jdk1.5:1.4-SNAPSHOT:compile
> The stageof lib depends on the jdk1.5 qualified commons and commons-xml libs.
> When I do a dependency:tree on an upper level webapp that depends on this stageof lib:
> [INFO] org.company.project:webapp:war:1.13-SNAPSHOT
> [INFO] +- org.company.project:stageof:jar:jdk1.5:1.4-SNAPSHOT:compile
> [INFO] | +- org.company.commons:jar:1.4.0:compile
> [INFO] | \- org.company.commons:commons-xml:jar:1.4-SNAPSHOT:compile
> [INFO] +- org.company.commons:jar:jdk1.5:1.5-SNAPSHOT:compile
> ...
> it finds correctly the qualified version of stageof, but include non qualified commons and commons-xml.
> These unqualified versions are the dependencies of the also non qualified stageof-1.4-SNAPSHOT.
> From this behavior, I presume dependency plugin makes a mistake in looking from the wrong pom, probably not using the qualifier of the included dependency:
> <dependency>
> <groupId>org.company.project</groupId>
> <artifactId>stageof</artifactId>
> <version>1.4-SNAPSHOT</version>
> <scope>compile</scope>
> <classifier>jdk1.5</classifier>
> </dependency>
> Hope this is clear.
> I could provide an example if you can't reproduce easily.
> Actually, just adding a qualifier to the jar-plugin to produce the artifact and to the <dependency> section should do the job.
> rgds,
> jean
--
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: (MDEP-251) Artifacts qualifier are NOT taken into
accounts correctly
Posted by "Andreas Brieg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MDEP-251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Brieg updated MDEP-251:
-------------------------------
Attachment: test.maven-dependency-plugin.zip
I attached a file, which shows an incorrect behavior with classifiers. The project has a dependency on a zip file with no classifier. A second dependency is within a profile, which is active by default. The dependency in the profile uses a classifier. The maven dependency plugin tries to download the dependency, which is not in the profile, with the classifier of the dependency in the profile.
Please note that there must not exists any dependencies listed in the project in your maven repositories in order to demonstrate the incorrect behavior.
> Artifacts qualifier are NOT taken into accounts correctly
> ---------------------------------------------------------
>
> Key: MDEP-251
> URL: http://jira.codehaus.org/browse/MDEP-251
> Project: Maven 2.x Dependency Plugin
> Issue Type: Bug
> Affects Versions: 2.1
> Environment: OSX 10.6.2, java 1.6.0_17
> Reporter: Jean Seurin
> Assignee: Brian Fox
> Priority: Critical
> Attachments: test.maven-dependency-plugin.zip
>
>
> I just introduced some qualifier for some libs that require to be compiled in java5.
> I've been very confused when realizing that when packaging a webapp depending on those qualified artifacts, the non qualified versions are included instead.
> It seems to come from dependency plugin.
> Here is what happens:
> When I do a dependency:tree on an artifact that depends directly on qualified libs, I get something regular:
> [INFO] [dependency:tree {execution: default-cli}]
> [INFO] org.company.project:stageof:jar:1.4-SNAPSHOT
> [INFO] +- org.company.project:jar:jdk1.5:1.5-SNAPSHOT:compile
> ....
> [INFO] +- org.company.commons:commons-xml:jar:jdk1.5:1.4-SNAPSHOT:compile
> The stageof lib depends on the jdk1.5 qualified commons and commons-xml libs.
> When I do a dependency:tree on an upper level webapp that depends on this stageof lib:
> [INFO] org.company.project:webapp:war:1.13-SNAPSHOT
> [INFO] +- org.company.project:stageof:jar:jdk1.5:1.4-SNAPSHOT:compile
> [INFO] | +- org.company.commons:jar:1.4.0:compile
> [INFO] | \- org.company.commons:commons-xml:jar:1.4-SNAPSHOT:compile
> [INFO] +- org.company.commons:jar:jdk1.5:1.5-SNAPSHOT:compile
> ...
> it finds correctly the qualified version of stageof, but include non qualified commons and commons-xml.
> These unqualified versions are the dependencies of the also non qualified stageof-1.4-SNAPSHOT.
> From this behavior, I presume dependency plugin makes a mistake in looking from the wrong pom, probably not using the qualifier of the included dependency:
> <dependency>
> <groupId>org.company.project</groupId>
> <artifactId>stageof</artifactId>
> <version>1.4-SNAPSHOT</version>
> <scope>compile</scope>
> <classifier>jdk1.5</classifier>
> </dependency>
> Hope this is clear.
> I could provide an example if you can't reproduce easily.
> Actually, just adding a qualifier to the jar-plugin to produce the artifact and to the <dependency> section should do the job.
> rgds,
> jean
--
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] (MDEP-251) Artifacts qualifier are NOT taken into accounts
correctly
Posted by "Herve Boutemy (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MDEP-251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Herve Boutemy updated MDEP-251:
-------------------------------
Description:
I just introduced some qualifier for some libs that require to be compiled in java5.
I've been very confused when realizing that when packaging a webapp depending on those qualified artifacts, the non qualified versions are included instead.
It seems to come from dependency plugin.
Here is what happens:
When I do a dependency:tree on an artifact that depends directly on qualified libs, I get something regular:
{noformat}[INFO] [dependency:tree {execution: default-cli}]
[INFO] org.company.project:stageof:jar:1.4-SNAPSHOT
[INFO] +- org.company.project:jar:jdk1.5:1.5-SNAPSHOT:compile
....
[INFO] +- org.company.commons:commons-xml:jar:jdk1.5:1.4-SNAPSHOT:compile{noformat}
The stageof lib depends on the jdk1.5 qualified commons and commons-xml libs.
When I do a dependency:tree on an upper level webapp that depends on this stageof lib:
{noformat}[INFO] org.company.project:webapp:war:1.13-SNAPSHOT
[INFO] +- org.company.project:stageof:jar:jdk1.5:1.4-SNAPSHOT:compile
[INFO] | +- org.company.commons:jar:1.4.0:compile
[INFO] | \- org.company.commons:commons-xml:jar:1.4-SNAPSHOT:compile
[INFO] +- org.company.commons:jar:jdk1.5:1.5-SNAPSHOT:compile
...{noformat}
it finds correctly the qualified version of stageof, but include non qualified commons and commons-xml.
These unqualified versions are the dependencies of the also non qualified stageof-1.4-SNAPSHOT.
>From this behavior, I presume dependency plugin makes a mistake in looking from the wrong pom, probably not using the qualifier of the included dependency:
{code:xml} <dependency>
<groupId>org.company.project</groupId>
<artifactId>stageof</artifactId>
<version>1.4-SNAPSHOT</version>
<scope>compile</scope>
<classifier>jdk1.5</classifier>
</dependency>{code}
Hope this is clear.
I could provide an example if you can't reproduce easily.
Actually, just adding a qualifier to the jar-plugin to produce the artifact and to the <dependency> section should do the job.
rgds,
jean
was:
I just introduced some qualifier for some libs that require to be compiled in java5.
I've been very confused when realizing that when packaging a webapp depending on those qualified artifacts, the non qualified versions are included instead.
It seems to come from dependency plugin.
Here is what happens:
When I do a dependency:tree on an artifact that depends directly on qualified libs, I get something regular:
[INFO] [dependency:tree {execution: default-cli}]
[INFO] org.company.project:stageof:jar:1.4-SNAPSHOT
[INFO] +- org.company.project:jar:jdk1.5:1.5-SNAPSHOT:compile
....
[INFO] +- org.company.commons:commons-xml:jar:jdk1.5:1.4-SNAPSHOT:compile
The stageof lib depends on the jdk1.5 qualified commons and commons-xml libs.
When I do a dependency:tree on an upper level webapp that depends on this stageof lib:
[INFO] org.company.project:webapp:war:1.13-SNAPSHOT
[INFO] +- org.company.project:stageof:jar:jdk1.5:1.4-SNAPSHOT:compile
[INFO] | +- org.company.commons:jar:1.4.0:compile
[INFO] | \- org.company.commons:commons-xml:jar:1.4-SNAPSHOT:compile
[INFO] +- org.company.commons:jar:jdk1.5:1.5-SNAPSHOT:compile
...
it finds correctly the qualified version of stageof, but include non qualified commons and commons-xml.
These unqualified versions are the dependencies of the also non qualified stageof-1.4-SNAPSHOT.
>From this behavior, I presume dependency plugin makes a mistake in looking from the wrong pom, probably not using the qualifier of the included dependency:
<dependency>
<groupId>org.company.project</groupId>
<artifactId>stageof</artifactId>
<version>1.4-SNAPSHOT</version>
<scope>compile</scope>
<classifier>jdk1.5</classifier>
</dependency>
Hope this is clear.
I could provide an example if you can't reproduce easily.
Actually, just adding a qualifier to the jar-plugin to produce the artifact and to the <dependency> section should do the job.
rgds,
jean
> Artifacts qualifier are NOT taken into accounts correctly
> ---------------------------------------------------------
>
> Key: MDEP-251
> URL: https://jira.codehaus.org/browse/MDEP-251
> Project: Maven 2.x Dependency Plugin
> Issue Type: Bug
> Components: tree
> Affects Versions: 2.1
> Environment: OSX 10.6.2, java 1.6.0_17
> Reporter: Jean Seurin
> Assignee: Brian Fox
> Priority: Critical
> Attachments: test.maven-dependency-plugin.zip
>
>
> I just introduced some qualifier for some libs that require to be compiled in java5.
> I've been very confused when realizing that when packaging a webapp depending on those qualified artifacts, the non qualified versions are included instead.
> It seems to come from dependency plugin.
> Here is what happens:
> When I do a dependency:tree on an artifact that depends directly on qualified libs, I get something regular:
> {noformat}[INFO] [dependency:tree {execution: default-cli}]
> [INFO] org.company.project:stageof:jar:1.4-SNAPSHOT
> [INFO] +- org.company.project:jar:jdk1.5:1.5-SNAPSHOT:compile
> ....
> [INFO] +- org.company.commons:commons-xml:jar:jdk1.5:1.4-SNAPSHOT:compile{noformat}
> The stageof lib depends on the jdk1.5 qualified commons and commons-xml libs.
> When I do a dependency:tree on an upper level webapp that depends on this stageof lib:
> {noformat}[INFO] org.company.project:webapp:war:1.13-SNAPSHOT
> [INFO] +- org.company.project:stageof:jar:jdk1.5:1.4-SNAPSHOT:compile
> [INFO] | +- org.company.commons:jar:1.4.0:compile
> [INFO] | \- org.company.commons:commons-xml:jar:1.4-SNAPSHOT:compile
> [INFO] +- org.company.commons:jar:jdk1.5:1.5-SNAPSHOT:compile
> ...{noformat}
> it finds correctly the qualified version of stageof, but include non qualified commons and commons-xml.
> These unqualified versions are the dependencies of the also non qualified stageof-1.4-SNAPSHOT.
> From this behavior, I presume dependency plugin makes a mistake in looking from the wrong pom, probably not using the qualifier of the included dependency:
> {code:xml} <dependency>
> <groupId>org.company.project</groupId>
> <artifactId>stageof</artifactId>
> <version>1.4-SNAPSHOT</version>
> <scope>compile</scope>
> <classifier>jdk1.5</classifier>
> </dependency>{code}
> Hope this is clear.
> I could provide an example if you can't reproduce easily.
> Actually, just adding a qualifier to the jar-plugin to produce the artifact and to the <dependency> section should do the job.
> rgds,
> jean
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MDEP-251) Artifacts qualifier are NOT taken into
accounts correctly
Posted by "Brian Fox (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MDEP-251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=222926#action_222926 ]
Brian Fox commented on MDEP-251:
--------------------------------
Please provide a test project. Also the dependency plugin _reports_ on the resolution it doesn't do the resolution itself. It appears to me you are talking about a core issue and not one in the plugin but without a sample I can't be sure.
> Artifacts qualifier are NOT taken into accounts correctly
> ---------------------------------------------------------
>
> Key: MDEP-251
> URL: http://jira.codehaus.org/browse/MDEP-251
> Project: Maven 2.x Dependency Plugin
> Issue Type: Bug
> Affects Versions: 2.1
> Environment: OSX 10.6.2, java 1.6.0_17
> Reporter: Jean Seurin
> Assignee: Brian Fox
> Priority: Critical
>
> I just introduced some qualifier for some libs that require to be compiled in java5.
> I've been very confused when realizing that when packaging a webapp depending on those qualified artifacts, the non qualified versions are included instead.
> It seems to come from dependency plugin.
> Here is what happens:
> When I do a dependency:tree on an artifact that depends directly on qualified libs, I get something regular:
> [INFO] [dependency:tree {execution: default-cli}]
> [INFO] org.company.project:stageof:jar:1.4-SNAPSHOT
> [INFO] +- org.company.project:jar:jdk1.5:1.5-SNAPSHOT:compile
> ....
> [INFO] +- org.company.commons:commons-xml:jar:jdk1.5:1.4-SNAPSHOT:compile
> The stageof lib depends on the jdk1.5 qualified commons and commons-xml libs.
> When I do a dependency:tree on an upper level webapp that depends on this stageof lib:
> [INFO] org.company.project:webapp:war:1.13-SNAPSHOT
> [INFO] +- org.company.project:stageof:jar:jdk1.5:1.4-SNAPSHOT:compile
> [INFO] | +- org.company.commons:jar:1.4.0:compile
> [INFO] | \- org.company.commons:commons-xml:jar:1.4-SNAPSHOT:compile
> [INFO] +- org.company.commons:jar:jdk1.5:1.5-SNAPSHOT:compile
> ...
> it finds correctly the qualified version of stageof, but include non qualified commons and commons-xml.
> These unqualified versions are the dependencies of the also non qualified stageof-1.4-SNAPSHOT.
> From this behavior, I presume dependency plugin makes a mistake in looking from the wrong pom, probably not using the qualifier of the included dependency:
> <dependency>
> <groupId>org.company.project</groupId>
> <artifactId>stageof</artifactId>
> <version>1.4-SNAPSHOT</version>
> <scope>compile</scope>
> <classifier>jdk1.5</classifier>
> </dependency>
> Hope this is clear.
> I could provide an example if you can't reproduce easily.
> Actually, just adding a qualifier to the jar-plugin to produce the artifact and to the <dependency> section should do the job.
> rgds,
> jean
--
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] (MDEP-251) Artifacts qualifier are NOT taken into accounts
correctly
Posted by "Paul Gier (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MDEP-251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Gier updated MDEP-251:
---------------------------
Component/s: tree
> Artifacts qualifier are NOT taken into accounts correctly
> ---------------------------------------------------------
>
> Key: MDEP-251
> URL: https://jira.codehaus.org/browse/MDEP-251
> Project: Maven 2.x Dependency Plugin
> Issue Type: Bug
> Components: tree
> Affects Versions: 2.1
> Environment: OSX 10.6.2, java 1.6.0_17
> Reporter: Jean Seurin
> Assignee: Brian Fox
> Priority: Critical
> Attachments: test.maven-dependency-plugin.zip
>
>
> I just introduced some qualifier for some libs that require to be compiled in java5.
> I've been very confused when realizing that when packaging a webapp depending on those qualified artifacts, the non qualified versions are included instead.
> It seems to come from dependency plugin.
> Here is what happens:
> When I do a dependency:tree on an artifact that depends directly on qualified libs, I get something regular:
> [INFO] [dependency:tree {execution: default-cli}]
> [INFO] org.company.project:stageof:jar:1.4-SNAPSHOT
> [INFO] +- org.company.project:jar:jdk1.5:1.5-SNAPSHOT:compile
> ....
> [INFO] +- org.company.commons:commons-xml:jar:jdk1.5:1.4-SNAPSHOT:compile
> The stageof lib depends on the jdk1.5 qualified commons and commons-xml libs.
> When I do a dependency:tree on an upper level webapp that depends on this stageof lib:
> [INFO] org.company.project:webapp:war:1.13-SNAPSHOT
> [INFO] +- org.company.project:stageof:jar:jdk1.5:1.4-SNAPSHOT:compile
> [INFO] | +- org.company.commons:jar:1.4.0:compile
> [INFO] | \- org.company.commons:commons-xml:jar:1.4-SNAPSHOT:compile
> [INFO] +- org.company.commons:jar:jdk1.5:1.5-SNAPSHOT:compile
> ...
> it finds correctly the qualified version of stageof, but include non qualified commons and commons-xml.
> These unqualified versions are the dependencies of the also non qualified stageof-1.4-SNAPSHOT.
> From this behavior, I presume dependency plugin makes a mistake in looking from the wrong pom, probably not using the qualifier of the included dependency:
> <dependency>
> <groupId>org.company.project</groupId>
> <artifactId>stageof</artifactId>
> <version>1.4-SNAPSHOT</version>
> <scope>compile</scope>
> <classifier>jdk1.5</classifier>
> </dependency>
> Hope this is clear.
> I could provide an example if you can't reproduce easily.
> Actually, just adding a qualifier to the jar-plugin to produce the artifact and to the <dependency> section should do the job.
> rgds,
> jean
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MDEP-251) Artifacts qualifier are NOT taken into
accounts correctly
Posted by "Herve Boutemy (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MDEP-251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Herve Boutemy updated MDEP-251:
-------------------------------
Comment: was deleted
(was: Sorry, made a mistake on the issue name itself. It should be:
Artifacts qualifier are NOT taken into accounts correctly
There don't seem to be a way to edit this Issue name.)
> Artifacts qualifier are NOT taken into accounts correctly
> ---------------------------------------------------------
>
> Key: MDEP-251
> URL: http://jira.codehaus.org/browse/MDEP-251
> Project: Maven 2.x Dependency Plugin
> Issue Type: Bug
> Affects Versions: 2.1
> Environment: OSX 10.6.2, java 1.6.0_17
> Reporter: Jean Seurin
> Assignee: Brian Fox
> Priority: Critical
>
> I just introduced some qualifier for some libs that require to be compiled in java5.
> I've been very confused when realizing that when packaging a webapp depending on those qualified artifacts, the non qualified versions are included instead.
> It seems to come from dependency plugin.
> Here is what happens:
> When I do a dependency:tree on an artifact that depends directly on qualified libs, I get something regular:
> [INFO] [dependency:tree {execution: default-cli}]
> [INFO] org.company.project:stageof:jar:1.4-SNAPSHOT
> [INFO] +- org.company.project:jar:jdk1.5:1.5-SNAPSHOT:compile
> ....
> [INFO] +- org.company.commons:commons-xml:jar:jdk1.5:1.4-SNAPSHOT:compile
> The stageof lib depends on the jdk1.5 qualified commons and commons-xml libs.
> When I do a dependency:tree on an upper level webapp that depends on this stageof lib:
> [INFO] org.company.project:webapp:war:1.13-SNAPSHOT
> [INFO] +- org.company.project:stageof:jar:jdk1.5:1.4-SNAPSHOT:compile
> [INFO] | +- org.company.commons:jar:1.4.0:compile
> [INFO] | \- org.company.commons:commons-xml:jar:1.4-SNAPSHOT:compile
> [INFO] +- org.company.commons:jar:jdk1.5:1.5-SNAPSHOT:compile
> ...
> it finds correctly the qualified version of stageof, but include non qualified commons and commons-xml.
> These unqualified versions are the dependencies of the also non qualified stageof-1.4-SNAPSHOT.
> From this behavior, I presume dependency plugin makes a mistake in looking from the wrong pom, probably not using the qualifier of the included dependency:
> <dependency>
> <groupId>org.company.project</groupId>
> <artifactId>stageof</artifactId>
> <version>1.4-SNAPSHOT</version>
> <scope>compile</scope>
> <classifier>jdk1.5</classifier>
> </dependency>
> Hope this is clear.
> I could provide an example if you can't reproduce easily.
> Actually, just adding a qualifier to the jar-plugin to produce the artifact and to the <dependency> section should do the job.
> rgds,
> jean
--
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: (MDEP-251) Artifacts qualifier are NOT taken into
accounts correctly
Posted by "Herve Boutemy (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MDEP-251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Herve Boutemy updated MDEP-251:
-------------------------------
Summary: Artifacts qualifier are NOT taken into accounts correctly (was: Artifacts qualifier are taken into accounts correctly)
> Artifacts qualifier are NOT taken into accounts correctly
> ---------------------------------------------------------
>
> Key: MDEP-251
> URL: http://jira.codehaus.org/browse/MDEP-251
> Project: Maven 2.x Dependency Plugin
> Issue Type: Bug
> Affects Versions: 2.1
> Environment: OSX 10.6.2, java 1.6.0_17
> Reporter: Jean Seurin
> Assignee: Brian Fox
> Priority: Critical
>
> I just introduced some qualifier for some libs that require to be compiled in java5.
> I've been very confused when realizing that when packaging a webapp depending on those qualified artifacts, the non qualified versions are included instead.
> It seems to come from dependency plugin.
> Here is what happens:
> When I do a dependency:tree on an artifact that depends directly on qualified libs, I get something regular:
> [INFO] [dependency:tree {execution: default-cli}]
> [INFO] org.company.project:stageof:jar:1.4-SNAPSHOT
> [INFO] +- org.company.project:jar:jdk1.5:1.5-SNAPSHOT:compile
> ....
> [INFO] +- org.company.commons:commons-xml:jar:jdk1.5:1.4-SNAPSHOT:compile
> The stageof lib depends on the jdk1.5 qualified commons and commons-xml libs.
> When I do a dependency:tree on an upper level webapp that depends on this stageof lib:
> [INFO] org.company.project:webapp:war:1.13-SNAPSHOT
> [INFO] +- org.company.project:stageof:jar:jdk1.5:1.4-SNAPSHOT:compile
> [INFO] | +- org.company.commons:jar:1.4.0:compile
> [INFO] | \- org.company.commons:commons-xml:jar:1.4-SNAPSHOT:compile
> [INFO] +- org.company.commons:jar:jdk1.5:1.5-SNAPSHOT:compile
> ...
> it finds correctly the qualified version of stageof, but include non qualified commons and commons-xml.
> These unqualified versions are the dependencies of the also non qualified stageof-1.4-SNAPSHOT.
> From this behavior, I presume dependency plugin makes a mistake in looking from the wrong pom, probably not using the qualifier of the included dependency:
> <dependency>
> <groupId>org.company.project</groupId>
> <artifactId>stageof</artifactId>
> <version>1.4-SNAPSHOT</version>
> <scope>compile</scope>
> <classifier>jdk1.5</classifier>
> </dependency>
> Hope this is clear.
> I could provide an example if you can't reproduce easily.
> Actually, just adding a qualifier to the jar-plugin to produce the artifact and to the <dependency> section should do the job.
> rgds,
> jean
--
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: (MDEP-251) Artifacts qualifier are NOT taken into
accounts correctly
Posted by "Joerg Schaible (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MDEP-251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=243724#action_243724 ]
Joerg Schaible commented on MDEP-251:
-------------------------------------
@Andreas Brieg: Maven is absolute correct. Different classifier (even "no classifier") address distinct dependencies. What you do in your profile is simply adding a second dependency and Maven behaves accordingly.
> Artifacts qualifier are NOT taken into accounts correctly
> ---------------------------------------------------------
>
> Key: MDEP-251
> URL: http://jira.codehaus.org/browse/MDEP-251
> Project: Maven 2.x Dependency Plugin
> Issue Type: Bug
> Affects Versions: 2.1
> Environment: OSX 10.6.2, java 1.6.0_17
> Reporter: Jean Seurin
> Assignee: Brian Fox
> Priority: Critical
> Attachments: test.maven-dependency-plugin.zip
>
>
> I just introduced some qualifier for some libs that require to be compiled in java5.
> I've been very confused when realizing that when packaging a webapp depending on those qualified artifacts, the non qualified versions are included instead.
> It seems to come from dependency plugin.
> Here is what happens:
> When I do a dependency:tree on an artifact that depends directly on qualified libs, I get something regular:
> [INFO] [dependency:tree {execution: default-cli}]
> [INFO] org.company.project:stageof:jar:1.4-SNAPSHOT
> [INFO] +- org.company.project:jar:jdk1.5:1.5-SNAPSHOT:compile
> ....
> [INFO] +- org.company.commons:commons-xml:jar:jdk1.5:1.4-SNAPSHOT:compile
> The stageof lib depends on the jdk1.5 qualified commons and commons-xml libs.
> When I do a dependency:tree on an upper level webapp that depends on this stageof lib:
> [INFO] org.company.project:webapp:war:1.13-SNAPSHOT
> [INFO] +- org.company.project:stageof:jar:jdk1.5:1.4-SNAPSHOT:compile
> [INFO] | +- org.company.commons:jar:1.4.0:compile
> [INFO] | \- org.company.commons:commons-xml:jar:1.4-SNAPSHOT:compile
> [INFO] +- org.company.commons:jar:jdk1.5:1.5-SNAPSHOT:compile
> ...
> it finds correctly the qualified version of stageof, but include non qualified commons and commons-xml.
> These unqualified versions are the dependencies of the also non qualified stageof-1.4-SNAPSHOT.
> From this behavior, I presume dependency plugin makes a mistake in looking from the wrong pom, probably not using the qualifier of the included dependency:
> <dependency>
> <groupId>org.company.project</groupId>
> <artifactId>stageof</artifactId>
> <version>1.4-SNAPSHOT</version>
> <scope>compile</scope>
> <classifier>jdk1.5</classifier>
> </dependency>
> Hope this is clear.
> I could provide an example if you can't reproduce easily.
> Actually, just adding a qualifier to the jar-plugin to produce the artifact and to the <dependency> section should do the job.
> rgds,
> jean
--
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