Maven release plugin : Problem when releasing modules

[Christophe Hamerling - EBM WebSourcing <ch...@ebmwebsourcing.com>]

I am doing some test with the maven release plugin.
I have two modules module1 and module2 with a pom parent.
The pom parent is defined as SNAPSHOT version and the two modules have a 
reference to the pom parent.
When trying to release, here is the error:

chamerling@EBM-14:~/dev/test/trunk$ mvn release:prepare 
-Dmaven.username=chamerling
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO]   Petals
[INFO]   module1
[INFO]   module2
[INFO] Searching repository for plugin with prefix: 'release'.
[INFO] 
----------------------------------------------------------------------------
[INFO] Building Petals
[INFO]    task-segment: [release:prepare] (aggregator-style)
[INFO] 
----------------------------------------------------------------------------
[INFO] [release:prepare]
[INFO] Verifying that there are no local modifications...
[INFO] Executing: svn --non-interactive status
[INFO] Working directory: /home/chamerling/dev/test/trunk
[INFO] Checking dependencies and plugins for snapshots ...
What is the release version for "Petals"? 
(org.objectweb.petals:petals-test) : : 1
What is the release version for "module1"? 
(org.objectweb.petals:module1) 1.0: :
What is the release version for "module2"? 
(org.objectweb.petals:module2) 1.0: :
What is SCM release tag or label for "Petals"? 
(org.objectweb.petals:petals-test) petals-test-1: :
[INFO] 
------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO] 
------------------------------------------------------------------------
[INFO] null
[INFO] 
------------------------------------------------------------------------
[INFO] Trace
java.lang.NullPointerException
        at 
org.apache.maven.plugins.release.phase.MapVersionsPhase.execute(MapVersionsPhase.java:90)
        at 
org.apache.maven.plugins.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:139)
        at 
org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareReleaseMojo.java:106)
        at 
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
        at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
        at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:488)
        at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:458)
        at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
        at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:219)
        at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
        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:256)
        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)
[INFO] 
------------------------------------------------------------------------
[INFO] Total time: 18 seconds
[INFO] Finished at: Wed Mar 07 15:49:48 GMT+01:00 2007
[INFO] Final Memory: 4M/8M
[INFO] 
------------------------------------------------------------------------


Any ideas ?

Thanks

Christophe Hamerling