[ 
http://jira.codehaus.org/browse/MNBMODULE-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Milos Kleint closed MNBMODULE-38.
---------------------------------

       Resolution: Fixed
    Fix Version/s: 3.0

implemented. The classes used in module jar + Class-Path entries are checked 
against the classes collected from the dependency tree. If a class is found 
that cannot be reached at runtime, the build either fails or warns.

> verify NetBeans runtime dependency information.
> -----------------------------------------------
>
>                 Key: MNBMODULE-38
>                 URL: http://jira.codehaus.org/browse/MNBMODULE-38
>             Project: Maven 2.x Netbeans Module Plugin
>          Issue Type: New Feature
>    Affects Versions: 2.6
>            Reporter: Milos Kleint
>            Assignee: Milos Kleint
>             Fix For: 3.0
>
>
> currently it's frequent that due to transitive dependencies, you can use 
> classes from trans. deps and compile his module, but the module dependency is 
> not added in the manifest and the runtime execution fails. We need to check 
> somehow what modules are used by the project's classes and verify that 
> against the generated manifest metadata.

-- 
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


Reply via email to