Resolution: Not A Problem
Affects Version/s: 2.6
Fix Version/s: None
The Introduction to the Dependency Mechanism page 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.
|Workflow||jira [ 12957852 ]||Default workflow, editable Closed status [ 12994774 ]|
|Project Import||Sun Apr 05 23:36:55 UTC 2015 [ 1428277015909 ]|
|Workflow||jira [ 12720354 ]||Default workflow, editable Closed status [ 12750148 ]|
|Project Import||Sun Apr 05 09:57:13 UTC 2015 [ 1428227833271 ]|
|Resolution||Not A Bug [ 6 ]|
|Status||Open [ 1 ]||Closed [ 6 ]|
|Field||Original Value||New Value|
|Attachment||mear-143.zip [ 57063 ]|