[
https://jira.codehaus.org/browse/MNBMODULE-154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse Glick closed MNBMODULE-154.
---------------------------------
Resolution: Cannot Reproduce
Working today; maybe just needed a clean build?
> Excluded runtime dependencies nonetheless listed in Class-Path
> --------------------------------------------------------------
>
> Key: MNBMODULE-154
> URL: https://jira.codehaus.org/browse/MNBMODULE-154
> Project: Maven NetBeans Module Plugin
> Issue Type: Bug
> Affects Versions: 3.6
> Environment: Maven 3.0.3
> Reporter: Jesse Glick
> Assignee: Jesse Glick
> Priority: Minor
>
> If an NBM project M has a compile dep on a JAR project A, and a runtime dep
> on a JAR project B which in turn has a dep on project C, but C is excluded
> from M, {{modules/ext/}} in the built NBM contains {{A.jar}}, as expected;
> and {{B.jar}}, possibly as expected, with no {{C.jar}}, as expected. Yet
> {{Class-Path}} in the generated module lists all three JARs, which is
> definitely wrong. {{Maven-Class-Path}} lists just {{A}} and {{B}}.
--
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
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
