[ http://jira.codehaus.org/browse/MDEP-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_127997 ]
B. Garvelink commented on MDEP-124: ----------------------------------- Likewise, if you run {{dependency-analyze[Only]}} on a project without any source code in it (the plugin is defined in my root pom, and I'm building an EAR module), all project dependencies are reported as unused declared. > Dependency incorrectly reported as "Unused declared" > ---------------------------------------------------- > > Key: MDEP-124 > URL: http://jira.codehaus.org/browse/MDEP-124 > Project: Maven 2.x Dependency Plugin > Issue Type: Bug > Components: analyze > Reporter: Olivier Dehon > Assignee: Brian Fox > > When a dependency is only required for a constant in a JAR, > dependency:analyze incorrectly reports the dependency as "Unused declared". > Example: > Constants.jar has 1 class called Constants.java: > {code} > package com.myco.util; > public class Constants > { > private Constants() {}; > public static final double PI = 3.14159; > } > {code} > Then App jar has App.java as: > {code} > package com.myco.app; > public class App > { > public static void main( String[] args ) > { > System.out.println( com.myco.util.Constants.PI ); > } > } > {code} > Since the constant gets optimized away in the generated {{App.class}}, the > dependency is not detected, even though the project won't compile without it. -- 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