Hi,
Thanks for the help, looks like there were some network issues
that have not been fixed yet in my office. I would have to wait till
they are fixed and probably see if I still have the same issue. But
Justin, I am curious to know how you were able to know it was a snapshot
version of the plugin.
Thanks...
________________________________
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of nicolas de loof
Sent: Friday, April 18, 2008 2:52 AM
To: [email protected]
Subject: Re: [mojo-user] release perform null pointer exception
2.0-beta-8-20080418.064928-4 deployed with fix for this.
2008/4/17, Edelson, Justin <[EMAIL PROTECTED]>:
It looks like if goals==null, this will happen. But as near as I can
tell, this is hasn't been released yet. Are you using a snapshot version
of the release plugin (bad idea, imho).
________________________________
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 17, 2008 2:14 PM
To: [email protected]
Subject: [mojo-user] release perform null pointer exception
Hi All,
I have a NullPointerException while doing a release perform, not
able to figure out why. Here is the stack trace.
[INFO] [release:perform]
[INFO]
------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO]
------------------------------------------------------------------------
[INFO] null
[INFO]
------------------------------------------------------------------------
[INFO] Trace
java.lang.NullPointerException
at java.util.StringTokenizer.<init>(StringTokenizer.java:182)
at java.util.StringTokenizer.<init>(StringTokenizer.java:219)
at
org.codehaus.plexus.util.StringUtils.split(StringUtils.java:520)
at
org.codehaus.plexus.util.StringUtils.split(StringUtils.java:484)
at
org.apache.maven.plugins.release.PerformReleaseMojo.execute(PerformRelea
seMojo.java:101)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMa
nager.java:443)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default
LifecycleExecutor.java:539)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoa
l(DefaultLifecycleExecutor.java:493)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultL
ifecycleExecutor.java:463)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle
Failures(DefaultLifecycleExecutor.java:311)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
DefaultLifecycleExecutor.java:224)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec
ycleExecutor.java:143)
at
org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
a:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.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)
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 2 seconds
[INFO] Finished at: Thu Apr 17 13:54:32 EDT 2008
[INFO] Final Memory: 6M/127M
[INFO]
------------------------------------------------------------------------
Could somebosy please let me know if there is a way to debug this.
Thanks...
