so, the quick workaround is to add a <connection> element and just copy the content of the developerConnection (or provide a more proper value, if you have any).
apparently the beta-5 release was not deployed. On 12/21/06, Valerio Schiavoni <[EMAIL PROTECTED]> wrote:
i'm hitting this one: http://jira.codehaus.org/browse/MRELEASE-108 i need to specify the version o the plugin in the pom.. On 12/21/06, Valerio Schiavoni <[EMAIL PROTECTED]> wrote: > > hello everyone, > i'm trying to use the release plugin. > I run it with: > > mvn -Dusername=schiavoni release:clean release:prepare -DdryRun=true > > (to be sure that nothing wrong goes to my cvs repository and to the > maven repository) > > and i get the folliwing stacktrace: > > [INFO] Transforming 'Website Model'... > [INFO] > ------------------------------------------------------------------------ > [ERROR] FATAL ERROR > [INFO] > ------------------------------------------------------------------------ > [INFO] null > [INFO] > ------------------------------------------------------------------------ > [INFO] Trace > java.lang.NullPointerException > at java.util.Hashtable.put(Hashtable.java:394) > at java.util.Properties.setProperty(Properties.java:143) > at org.apache.maven.plugins.release > .config.PropertiesReleaseConfigurationStore.write( > PropertiesReleaseConfigurationStore.java :225) > at org.apache.maven.plugins.release.config.PropertiesReleaseConfigurationStore.write > (PropertiesReleaseConfigurationStore.java:149) > at org.apache.maven.plugins.release.DefaultReleaseManager. > prepare(DefaultReleaseManager.java :145) > 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:597) > 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) > > > I got a pom.xml.tag and a release.properties files created in the root > directory of my project. > The version in the pom.xml.tag is properly changed to 1.1 (was > 1.1-SNAPSHOT) and in the release.properties there are the parameters i > passed during the release :prepare execution, just before the NPE. > the parameters I passed are: 1.1 as releae, 1.1 as scm tag, and > 1.2-SNAPSHOT as new development version. > > any idea ? > > thanks a lot, > valerio > -- > http://valerioschiavoni.blogspot.com > http://jroller.com/page/vschiavoni -- http://valerioschiavoni.blogspot.com http://jroller.com/page/vschiavoni
-- http://valerioschiavoni.blogspot.com http://jroller.com/page/vschiavoni
