[
https://jira.codehaus.org/browse/MJBOSSPACK-40?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=274926#comment-274926
]
Anders Hammar commented on MJBOSSPACK-40:
-----------------------------------------
I can reproduce this with Maven 3.0, 3.0.1, 3.0.2, and 3.0.3. But with Maven
2.2.1 the correct behavior (3rd party jar not included in sar) is seen.
Not sure if this is a Maven 3 issue or something in this plugin working
differently with Maven 3.
What is strange is that it's enough to remove the compile scope declaration in
the dependencyMgmt section of the pom and it will not be included (when built
with Maven 3). As compile scope is default it should not make a difference
though (but it does) - strange!
> Transitive dependencies specified in dependencyManagement section included in
> sar
> ---------------------------------------------------------------------------------
>
> Key: MJBOSSPACK-40
> URL: https://jira.codehaus.org/browse/MJBOSSPACK-40
> Project: Maven 2.x JBoss Packaging Plugin
> Issue Type: Bug
> Components: sar
> Affects Versions: 2.2
> Environment: Windows 7, Maven 3.0.3, JDK 1.6.0.24 x64
> Reporter: Oleg Koptelov
> Attachments: jboss-sar-test.zip
>
>
> Parent project contains 2 modules: sar-module and jar-module. sar-module
> depends on jar-module with scope=provided. jar-module depends on 3rd party
> jar with scope=compile. Dependency on the 3rd party jar specified in
> dependencyManagement section of the parent pom. Execution of mvn clean
> package command produces sar which contains the 3rd party jar in the lib
> directory. If the jar removed from dependencyManagement, the jar is not
> included in the sar.
> Zip with the setup to reproduce the issue is attached.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
