[
http://jira.codehaus.org/browse/MCLIRR-14?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=142011#action_142011
]
Arnaud Heritier commented on MCLIRR-14:
---------------------------------------
This bug is fixed with bcel 5.2.
It seems that it is not related to the scope or the optional flag of the
dependency but on some cases not correctly handled by bcel.
> Fail's checking if dependencies are declared as provided
> --------------------------------------------------------
>
> Key: MCLIRR-14
> URL: http://jira.codehaus.org/browse/MCLIRR-14
> Project: Maven 2.x Clirr Plugin
> Issue Type: Bug
> Affects Versions: 2.2.1
> Environment: N/A
> Reporter: Arnaud Heritier
> Assignee: Arnaud Heritier
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> The same as MCLIRR-7 in a complex project.
> {code}
> java.lang.ClassNotFoundException: javax.servlet.Filter not found.
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] FATAL ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] null
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Trace
> java.lang.NullPointerException
> at
> org.apache.bcel.classfile.JavaClass.getAllInterfaces(JavaClass.java:808)
> at
> net.sf.clirr.core.internal.bcel.BcelJavaType.getAllInterfaces(BcelJavaType.java:78)
> at
> net.sf.clirr.core.internal.checks.InterfaceSetCheck.check(InterfaceSetCheck.java:58)
> at net.sf.clirr.core.Checker.runClassChecks(Checker.java:190)
> at net.sf.clirr.core.Checker.reportDiffs(Checker.java:136)
> at
> org.codehaus.mojo.clirr.AbstractClirrMojo.executeClirr(AbstractClirrMojo.java:227)
> at org.codehaus.mojo.clirr.ClirrReport.doReport(ClirrReport.java:249)
> at org.codehaus.mojo.clirr.ClirrReport.generate(ClirrReport.java:225)
> at org.codehaus.mojo.clirr.ClirrReport.generate(ClirrReport.java:376)
> at org.codehaus.mojo.clirr.ClirrReport.execute(ClirrReport.java:188)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> {code}
> I can't yet reproduce it with a simple test case....
> In my case the servlet-api is defined as provided
--
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
