[
http://jira.codehaus.org/browse/MJBOSSPACK-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Gier updated MJBOSSPACK-2:
-------------------------------
Fix Version/s: 1.0-alpha-1
If A is a runtime dependency, then I believe you would want the dependency
included in the sar. If the dependency is set to a "provided" scope, the
dependeny (direct or transitive) is not included in the sar. At least this is
how it's working in the current snapshot.
I will mark this as won't fix unless some more detail can be provided.
> Dependency scope not respected
> ------------------------------
>
> Key: MJBOSSPACK-2
> URL: http://jira.codehaus.org/browse/MJBOSSPACK-2
> Project: Maven 2.x JBoss Packaging Plugin
> Issue Type: Bug
> Reporter: Frank Cornelis
> Fix For: 1.0-alpha-1
>
>
> When you create a SAR using jboss-packaging-maven-plugin with dependencies:
> A (runtime) -> B
> C (provided) -> B
> with A, B, C artifacts and where '->' means transitive dependency,
> then B should not be packaged under lib/ within the SAR.
--
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
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
