You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Laird Nelson (JIRA)" <ji...@codehaus.org> on 2011/09/28 06:20:17 UTC
[jira] Created: (MEAR-143) Plugin does not respect transitive
dependency scopes properly
Plugin does not respect transitive dependency scopes properly
-------------------------------------------------------------
Key: MEAR-143
URL: https://jira.codehaus.org/browse/MEAR-143
Project: Maven 2.x Ear Plugin
Issue Type: Bug
Affects Versions: 2.6
Reporter: Laird Nelson
The [Introduction to the Dependency Mechanism page|http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Dependency_Scope] has a handy table for deciding what to do with transitive dependencies and various scopes. The Maven ear plugin does not honor it in all cases.
Suppose I have a {{.jar}} file. Its name is {{b.jar}}. It declares a {{runtime}} dependency on {{a.jar}}.
Suppose now I have an {{.ear}} project. It declares a {{compile}} scope dependency on {{b.jar}}.
By the rules of the chart, {{a.jar}} should end up being a {{runtime}} dependency (transitively) of the {{.ear}}, and should be included in the {{lib}} directory. It is not.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MEAR-143) Plugin does not respect transitive
dependency scopes properly
Posted by "Laird Nelson (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MEAR-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=280178#comment-280178 ]
Laird Nelson commented on MEAR-143:
-----------------------------------
I was under the impression that if I "overrode" the scope the overridden scope would be honored?
Note that the dependencyManagement section initially defines mear-143-leaf's scope to be "test". But the actual dependency information in the ear file overrides the scope to be runtime. Shouldn't the scope of the dependency therefore be runtime? No?
> Plugin does not respect transitive dependency scopes properly
> -------------------------------------------------------------
>
> Key: MEAR-143
> URL: https://jira.codehaus.org/browse/MEAR-143
> Project: Maven 2.x Ear Plugin
> Issue Type: Bug
> Affects Versions: 2.6
> Reporter: Laird Nelson
> Attachments: mear-143.zip
>
>
> The [Introduction to the Dependency Mechanism page|http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Dependency_Scope] has a handy table for deciding what to do with transitive dependencies and various scopes. The Maven ear plugin does not honor it in all cases.
> Suppose I have a {{.jar}} file. Its name is {{b.jar}}. It declares a {{runtime}} dependency on {{a.jar}}.
> Suppose now I have an {{.ear}} project. It declares a {{compile}} scope dependency on {{b.jar}}.
> By the rules of the chart, {{a.jar}} should end up being a {{runtime}} dependency (transitively) of the {{.ear}}, and should be included in the {{lib}} directory. It is not.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MEAR-143) Plugin does not respect transitive
dependency scopes properly
Posted by "Joerg Schaible (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MEAR-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=280127#comment-280127 ]
Joerg Schaible commented on MEAR-143:
-------------------------------------
This works for us since years and I am sure we're not alone. So, without providing a small project that exhibit this behavior, this issue will probably simply closed with "cannot reproduce".
> Plugin does not respect transitive dependency scopes properly
> -------------------------------------------------------------
>
> Key: MEAR-143
> URL: https://jira.codehaus.org/browse/MEAR-143
> Project: Maven 2.x Ear Plugin
> Issue Type: Bug
> Affects Versions: 2.6
> Reporter: Laird Nelson
>
> The [Introduction to the Dependency Mechanism page|http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Dependency_Scope] has a handy table for deciding what to do with transitive dependencies and various scopes. The Maven ear plugin does not honor it in all cases.
> Suppose I have a {{.jar}} file. Its name is {{b.jar}}. It declares a {{runtime}} dependency on {{a.jar}}.
> Suppose now I have an {{.ear}} project. It declares a {{compile}} scope dependency on {{b.jar}}.
> By the rules of the chart, {{a.jar}} should end up being a {{runtime}} dependency (transitively) of the {{.ear}}, and should be included in the {{lib}} directory. It is not.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (MEAR-143) Plugin does not respect
transitive dependency scopes properly
Posted by "Laird Nelson (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MEAR-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=280178#comment-280178 ]
Laird Nelson edited comment on MEAR-143 at 9/28/11 8:48 AM:
------------------------------------------------------------
I was under the impression that if I "overrode" the scope the overridden scope would be honored?
Note that the dependencyManagement section initially defines mear-143-leaf's scope to be "test". But the actual dependency information in mear-143-middle overrides the scope to be runtime. Shouldn't the scope of the ear file's transitive mear-143-leaf dependency therefore be runtime? No?
was (Author: ljnelson):
I was under the impression that if I "overrode" the scope the overridden scope would be honored?
Note that the dependencyManagement section initially defines mear-143-leaf's scope to be "test". But the actual dependency information in the ear file overrides the scope to be runtime. Shouldn't the scope of the dependency therefore be runtime? No?
> Plugin does not respect transitive dependency scopes properly
> -------------------------------------------------------------
>
> Key: MEAR-143
> URL: https://jira.codehaus.org/browse/MEAR-143
> Project: Maven 2.x Ear Plugin
> Issue Type: Bug
> Affects Versions: 2.6
> Reporter: Laird Nelson
> Attachments: mear-143.zip
>
>
> The [Introduction to the Dependency Mechanism page|http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Dependency_Scope] has a handy table for deciding what to do with transitive dependencies and various scopes. The Maven ear plugin does not honor it in all cases.
> Suppose I have a {{.jar}} file. Its name is {{b.jar}}. It declares a {{runtime}} dependency on {{a.jar}}.
> Suppose now I have an {{.ear}} project. It declares a {{compile}} scope dependency on {{b.jar}}.
> By the rules of the chart, {{a.jar}} should end up being a {{runtime}} dependency (transitively) of the {{.ear}}, and should be included in the {{lib}} directory. It is not.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MEAR-143) Plugin does not respect transitive
dependency scopes properly
Posted by "Laird Nelson (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MEAR-143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Laird Nelson updated MEAR-143:
------------------------------
Attachment: mear-143.zip
A test case demonstrating the problem, or demonstrating my misunderstanding (one or the other).
Unzip and run mvn clean install and then look at the resulting .ear project (and study the pom.xml files).
Note that the .ear project does not contain mear-143-leaf.jar. It is my understanding that it should.
When dependency management of mear-143-leaf.jar is eliminated, this works as expected. Is this a bug or a misunderstanding on my part about how dependency management works?
> Plugin does not respect transitive dependency scopes properly
> -------------------------------------------------------------
>
> Key: MEAR-143
> URL: https://jira.codehaus.org/browse/MEAR-143
> Project: Maven 2.x Ear Plugin
> Issue Type: Bug
> Affects Versions: 2.6
> Reporter: Laird Nelson
> Attachments: mear-143.zip
>
>
> The [Introduction to the Dependency Mechanism page|http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Dependency_Scope] has a handy table for deciding what to do with transitive dependencies and various scopes. The Maven ear plugin does not honor it in all cases.
> Suppose I have a {{.jar}} file. Its name is {{b.jar}}. It declares a {{runtime}} dependency on {{a.jar}}.
> Suppose now I have an {{.ear}} project. It declares a {{compile}} scope dependency on {{b.jar}}.
> By the rules of the chart, {{a.jar}} should end up being a {{runtime}} dependency (transitively) of the {{.ear}}, and should be included in the {{lib}} directory. It is not.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MEAR-143) Plugin does not respect transitive
dependency scopes properly
Posted by "Laird Nelson (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MEAR-143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Laird Nelson closed MEAR-143.
-----------------------------
Resolution: Not A Bug
[This StackOverflow answer|http://stackoverflow.com/questions/7588492/maven-dependency-resolution-and-scope-overriding-not-just-another-newbie-questio/7597596#7597596] helped educate me on the fact that dependency management trumps dependency mediation even for scope, which I had not realized.
> Plugin does not respect transitive dependency scopes properly
> -------------------------------------------------------------
>
> Key: MEAR-143
> URL: https://jira.codehaus.org/browse/MEAR-143
> Project: Maven 2.x Ear Plugin
> Issue Type: Bug
> Affects Versions: 2.6
> Reporter: Laird Nelson
> Attachments: mear-143.zip
>
>
> The [Introduction to the Dependency Mechanism page|http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Dependency_Scope] has a handy table for deciding what to do with transitive dependencies and various scopes. The Maven ear plugin does not honor it in all cases.
> Suppose I have a {{.jar}} file. Its name is {{b.jar}}. It declares a {{runtime}} dependency on {{a.jar}}.
> Suppose now I have an {{.ear}} project. It declares a {{compile}} scope dependency on {{b.jar}}.
> By the rules of the chart, {{a.jar}} should end up being a {{runtime}} dependency (transitively) of the {{.ear}}, and should be included in the {{lib}} directory. It is not.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MEAR-143) Plugin does not respect transitive
dependency scopes properly
Posted by "Laird Nelson (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MEAR-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=280168#comment-280168 ]
Laird Nelson commented on MEAR-143:
-----------------------------------
Ha, got a test case that reproduces it; will attach it in a moment. The problem is with dependency management and scope overriding.
> Plugin does not respect transitive dependency scopes properly
> -------------------------------------------------------------
>
> Key: MEAR-143
> URL: https://jira.codehaus.org/browse/MEAR-143
> Project: Maven 2.x Ear Plugin
> Issue Type: Bug
> Affects Versions: 2.6
> Reporter: Laird Nelson
>
> The [Introduction to the Dependency Mechanism page|http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Dependency_Scope] has a handy table for deciding what to do with transitive dependencies and various scopes. The Maven ear plugin does not honor it in all cases.
> Suppose I have a {{.jar}} file. Its name is {{b.jar}}. It declares a {{runtime}} dependency on {{a.jar}}.
> Suppose now I have an {{.ear}} project. It declares a {{compile}} scope dependency on {{b.jar}}.
> By the rules of the chart, {{a.jar}} should end up being a {{runtime}} dependency (transitively) of the {{.ear}}, and should be included in the {{lib}} directory. It is not.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MEAR-143) Plugin does not respect transitive
dependency scopes properly
Posted by "Laird Nelson (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MEAR-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=280167#comment-280167 ]
Laird Nelson commented on MEAR-143:
-----------------------------------
Yes; interestingly the simple test case I'm putting together does not manifest this bug. There must be another wrinkle to it as this is demonstrable in our main product. I will (hopefully) attach my test case shortly or close the bug and chalk it up to magic. I am thinking that dependency management plays a part here.
> Plugin does not respect transitive dependency scopes properly
> -------------------------------------------------------------
>
> Key: MEAR-143
> URL: https://jira.codehaus.org/browse/MEAR-143
> Project: Maven 2.x Ear Plugin
> Issue Type: Bug
> Affects Versions: 2.6
> Reporter: Laird Nelson
>
> The [Introduction to the Dependency Mechanism page|http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Dependency_Scope] has a handy table for deciding what to do with transitive dependencies and various scopes. The Maven ear plugin does not honor it in all cases.
> Suppose I have a {{.jar}} file. Its name is {{b.jar}}. It declares a {{runtime}} dependency on {{a.jar}}.
> Suppose now I have an {{.ear}} project. It declares a {{compile}} scope dependency on {{b.jar}}.
> By the rules of the chart, {{a.jar}} should end up being a {{runtime}} dependency (transitively) of the {{.ear}}, and should be included in the {{lib}} directory. It is not.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (MEAR-143) Plugin does not respect
transitive dependency scopes properly
Posted by "Laird Nelson (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MEAR-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=280178#comment-280178 ]
Laird Nelson edited comment on MEAR-143 at 9/28/11 9:05 AM:
------------------------------------------------------------
I assume you're trying to point me to the text that reads:
{quote}
In addition, the version and scope of artifacts which are incorporated from transitive dependencies may also be controlled by specifying them in a dependency management section.
{quote}
But I was under the impression that if I "overrode" the scope the overridden scope would be honored? Note that the document to which you referred me does not address scope overriding.
Note as well that the {{<dependencyManagement>}} section initially defines {{mear-143-leaf}}'s scope to be {{test}}. But the actual {{<dependencies>}} information in {{mear-143-middle}} overrides the scope to be {{runtime}}. Shouldn't the scope of the ear file's transitive {{mear-143-leaf}} dependency therefore be {{runtime}}? No?
I based my theory off of http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Dependency_Management, specifically the section that begins "A second and very important use...". Note that in project B in that section project B overrides the scope of {{c}} to be {{runtime}}.
was (Author: ljnelson):
I assume you're trying to point me to the text that reads:
{quote}
In addition, the version and scope of artifacts which are incorporated from transitive dependencies may also be controlled by specifying them in a dependency management section.
{quote}
But I was under the impression that if I "overrode" the scope the overridden scope would be honored?
Note that the dependencyManagement section initially defines mear-143-leaf's scope to be "test". But the actual dependency information in mear-143-middle overrides the scope to be runtime. Shouldn't the scope of the ear file's transitive mear-143-leaf dependency therefore be runtime? No?
I based my theory off of http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Dependency_Management, specifically the section that begins "A second and very important use...". Note that in project B in that section project B overrides the scope of {{c}} to be {{runtime}}.
> Plugin does not respect transitive dependency scopes properly
> -------------------------------------------------------------
>
> Key: MEAR-143
> URL: https://jira.codehaus.org/browse/MEAR-143
> Project: Maven 2.x Ear Plugin
> Issue Type: Bug
> Affects Versions: 2.6
> Reporter: Laird Nelson
> Attachments: mear-143.zip
>
>
> The [Introduction to the Dependency Mechanism page|http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Dependency_Scope] has a handy table for deciding what to do with transitive dependencies and various scopes. The Maven ear plugin does not honor it in all cases.
> Suppose I have a {{.jar}} file. Its name is {{b.jar}}. It declares a {{runtime}} dependency on {{a.jar}}.
> Suppose now I have an {{.ear}} project. It declares a {{compile}} scope dependency on {{b.jar}}.
> By the rules of the chart, {{a.jar}} should end up being a {{runtime}} dependency (transitively) of the {{.ear}}, and should be included in the {{lib}} directory. It is not.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (MEAR-143) Plugin does not respect
transitive dependency scopes properly
Posted by "Laird Nelson (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MEAR-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=280178#comment-280178 ]
Laird Nelson edited comment on MEAR-143 at 9/28/11 8:53 AM:
------------------------------------------------------------
I assume you're trying to point me to the text that reads:
{quote}
In addition, the version and scope of artifacts which are incorporated from transitive dependencies may also be controlled by specifying them in a dependency management section.
{quote}
But I was under the impression that if I "overrode" the scope the overridden scope would be honored?
Note that the dependencyManagement section initially defines mear-143-leaf's scope to be "test". But the actual dependency information in mear-143-middle overrides the scope to be runtime. Shouldn't the scope of the ear file's transitive mear-143-leaf dependency therefore be runtime? No?
was (Author: ljnelson):
I was under the impression that if I "overrode" the scope the overridden scope would be honored?
Note that the dependencyManagement section initially defines mear-143-leaf's scope to be "test". But the actual dependency information in mear-143-middle overrides the scope to be runtime. Shouldn't the scope of the ear file's transitive mear-143-leaf dependency therefore be runtime? No?
> Plugin does not respect transitive dependency scopes properly
> -------------------------------------------------------------
>
> Key: MEAR-143
> URL: https://jira.codehaus.org/browse/MEAR-143
> Project: Maven 2.x Ear Plugin
> Issue Type: Bug
> Affects Versions: 2.6
> Reporter: Laird Nelson
> Attachments: mear-143.zip
>
>
> The [Introduction to the Dependency Mechanism page|http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Dependency_Scope] has a handy table for deciding what to do with transitive dependencies and various scopes. The Maven ear plugin does not honor it in all cases.
> Suppose I have a {{.jar}} file. Its name is {{b.jar}}. It declares a {{runtime}} dependency on {{a.jar}}.
> Suppose now I have an {{.ear}} project. It declares a {{compile}} scope dependency on {{b.jar}}.
> By the rules of the chart, {{a.jar}} should end up being a {{runtime}} dependency (transitively) of the {{.ear}}, and should be included in the {{lib}} directory. It is not.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MEAR-143) Plugin does not respect transitive
dependency scopes properly
Posted by "Joerg Schaible (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MEAR-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=280177#comment-280177 ]
Joerg Schaible commented on MEAR-143:
-------------------------------------
This is exactly how dependencyManagement works!
http://maven.apache.org/pom.html#Dependency_Management
> Plugin does not respect transitive dependency scopes properly
> -------------------------------------------------------------
>
> Key: MEAR-143
> URL: https://jira.codehaus.org/browse/MEAR-143
> Project: Maven 2.x Ear Plugin
> Issue Type: Bug
> Affects Versions: 2.6
> Reporter: Laird Nelson
> Attachments: mear-143.zip
>
>
> The [Introduction to the Dependency Mechanism page|http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Dependency_Scope] has a handy table for deciding what to do with transitive dependencies and various scopes. The Maven ear plugin does not honor it in all cases.
> Suppose I have a {{.jar}} file. Its name is {{b.jar}}. It declares a {{runtime}} dependency on {{a.jar}}.
> Suppose now I have an {{.ear}} project. It declares a {{compile}} scope dependency on {{b.jar}}.
> By the rules of the chart, {{a.jar}} should end up being a {{runtime}} dependency (transitively) of the {{.ear}}, and should be included in the {{lib}} directory. It is not.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (MEAR-143) Plugin does not respect
transitive dependency scopes properly
Posted by "Laird Nelson (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MEAR-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=280178#comment-280178 ]
Laird Nelson edited comment on MEAR-143 at 9/28/11 9:03 AM:
------------------------------------------------------------
I assume you're trying to point me to the text that reads:
{quote}
In addition, the version and scope of artifacts which are incorporated from transitive dependencies may also be controlled by specifying them in a dependency management section.
{quote}
But I was under the impression that if I "overrode" the scope the overridden scope would be honored?
Note that the dependencyManagement section initially defines mear-143-leaf's scope to be "test". But the actual dependency information in mear-143-middle overrides the scope to be runtime. Shouldn't the scope of the ear file's transitive mear-143-leaf dependency therefore be runtime? No?
I based my theory off of http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Dependency_Management, specifically the section that begins "A second and very important use...". Note that in project B in that section project B overrides the scope of {{c}} to be {{runtime}}.
was (Author: ljnelson):
I assume you're trying to point me to the text that reads:
{quote}
In addition, the version and scope of artifacts which are incorporated from transitive dependencies may also be controlled by specifying them in a dependency management section.
{quote}
But I was under the impression that if I "overrode" the scope the overridden scope would be honored?
Note that the dependencyManagement section initially defines mear-143-leaf's scope to be "test". But the actual dependency information in mear-143-middle overrides the scope to be runtime. Shouldn't the scope of the ear file's transitive mear-143-leaf dependency therefore be runtime? No?
> Plugin does not respect transitive dependency scopes properly
> -------------------------------------------------------------
>
> Key: MEAR-143
> URL: https://jira.codehaus.org/browse/MEAR-143
> Project: Maven 2.x Ear Plugin
> Issue Type: Bug
> Affects Versions: 2.6
> Reporter: Laird Nelson
> Attachments: mear-143.zip
>
>
> The [Introduction to the Dependency Mechanism page|http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Dependency_Scope] has a handy table for deciding what to do with transitive dependencies and various scopes. The Maven ear plugin does not honor it in all cases.
> Suppose I have a {{.jar}} file. Its name is {{b.jar}}. It declares a {{runtime}} dependency on {{a.jar}}.
> Suppose now I have an {{.ear}} project. It declares a {{compile}} scope dependency on {{b.jar}}.
> By the rules of the chart, {{a.jar}} should end up being a {{runtime}} dependency (transitively) of the {{.ear}}, and should be included in the {{lib}} directory. It is not.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira