[ http://jira.codehaus.org/browse/MJAR-31?page=comments#action_63464 ]
Jerome Lacoste commented on MJAR-31: ------------------------------------ On 4/13/06, Tim Kettler <tim.kettler@ .edu> wrote: > I just deleted my local repo and checked out the latest versions of the jar > and webstart > plugins from svn and can't reproduce the second NPE from MJAR-31 anymore. So > this is fixed > somehow already (at least for me). Thanks for the report. I lean toward closing the issue and reopening it if someone rereports it. The whole thing is fishy and I'd rather know why the getArtifact() can return null before making the change. I answered to Brett on the devel list if it is possible to make MavenProject#setArtifact throw an NPE if null is passed. If you encounter that issue, consider making that change yourself. > [webstart] NPE when signing dependencies > ---------------------------------------- > > Key: MJAR-31 > URL: http://jira.codehaus.org/browse/MJAR-31 > Project: Maven 2.x Jar Plugin > Type: Bug > Environment: WinXP > Maven 2.0.2 > Latest maven-jar-plugin from SVN > Latest webstart checkout > Reporter: Michael Böckling > Priority: Critical > Attachments: MOJO-295.diff > > > In JarSignMojo, the call to this.signedjar.getPath() produces a NPE, because > in JnlpMojo:863, signJar.setSignedJar() has been commented out. > Stacktrace: > [debug] jarsigner > executable=[C:\Programme\Java\jdk1.5.0_06\jre\..\bin\jarsigner > .exe] > [INFO] > ------------------------------------------------------------------------- > --- > [ERROR] BUILD ERROR > [INFO] > ------------------------------------------------------------------------- > --- > [INFO] Failure to run the plugin: > [INFO] > ------------------------------------------------------------------------- > --- > [DEBUG] Trace > org.apache.maven.lifecycle.LifecycleExecutionException: Failure to run the > plugi > n: > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa > ultLifecycleExecutor.java:556) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi > fecycle(DefaultLifecycleExecutor.java:472) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau > ltLifecycleExecutor.java:451) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan > dleFailures(DefaultLifecycleExecutor.java:303) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen > ts(DefaultLifecycleExecutor.java:270) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi > fecycleExecutor.java:139) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:249) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. > java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces > sorImpl.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) > Caused by: org.apache.maven.plugin.MojoExecutionException: Failure to run the > pl > ugin: > at org.codehaus.mojo.webstart.JnlpMojo.execute(JnlpMojo.java:479) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi > nManager.java:415) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa > ultLifecycleExecutor.java:531) > ... 16 more > Caused by: java.lang.NullPointerException > at > org.apache.maven.plugin.jar.JarSignMojo.signJar(JarSignMojo.java:227) > at > org.apache.maven.plugin.jar.JarSignMojo.execute(JarSignMojo.java:185) > at org.codehaus.mojo.webstart.JnlpMojo.signJars(JnlpMojo.java:865) > at org.codehaus.mojo.webstart.JnlpMojo.execute(JnlpMojo.java:441) > ... 18 more -- 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
