You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Chas Douglass <ch...@gmail.com> on 2006/05/16 02:22:46 UTC
Release Failure
I was successfully using "mvn release:prepare" on Friday. After the
upgrades and problems over the weekend I'm assuming something changed
(although it could be something I changed, of course).
When I execute it now I get a failure:
[INFO]
------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO]
------------------------------------------------------------------------
[INFO] null
[INFO]
------------------------------------------------------------------------
[INFO] Trace
java.lang.NullPointerException
at java.util.Hashtable.put(Hashtable.java:396)
at java.util.Properties.setProperty(Properties.java:128)
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: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)
(The full output can be seen at
http://www.floogle.net/JEC/catch.release.prepare)
The pom is:
<project xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>com.empireclassic</groupId>
<artifactId>JEC</artifactId>
<name>Java Empire Client</name>
<version>2.0.0-alpha-7</version>
<description>The GUI client for classic Empire</description>
<scm>
<developerConnection>scm:svn:svn://floogle.net/empire/JEC.tags/JEC-2.0.0-alpha-7</developerConnection>
</scm>
<build>
<resources>
<resource>
<filtering>true</filtering>
<directory>src/main/resources</directory>
<excludes>
<exclude>image/**</exclude>
</excludes>
</resource>
<resource>
<directory>src/main/resources</directory>
<includes>
<include>image/**</include>
</includes>
</resource>
</resources>
<plugins>
<plugin>
<artifactId>maven-compiler-plugin</artifactId>
<configuration>
<source>1.5</source>
<target>1.5</target>
</configuration>
</plugin>
<plugin>
<artifactId>maven-release-plugin</artifactId>
<configuration>
<tagBase>svn://floogle.net/empire/JEC.tags</tagBase>
</configuration>
</plugin>
<plugin>
<artifactId>maven-jar-plugin</artifactId>
<configuration>
<archive>
<manifestEntries>
<Class-Path>.</Class-Path>
</manifestEntries>
<manifest>
<packageName>com.empireclassic.jec</packageName>
<mainClass>com.empireclassic.jec.JEC</mainClass>
</manifest>
</archive>
</configuration>
</plugin>
</plugins>
</build>
<repositories>
<repository>
<id>empirerepo</id>
<url>http://empire.floogle.net/empirerepo</url>
</repository>
</repositories>
<dependencies>
<dependency>
<groupId>piccolo</groupId>
<artifactId>piccolo</artifactId>
<version>1.2</version>
</dependency>
<dependency>
<groupId>piccolo</groupId>
<artifactId>piccolox</artifactId>
<version>1.2</version>
</dependency>
<dependency>
<groupId>com.empireclassic</groupId>
<artifactId>RemoteEmpire</artifactId>
<version>1.0-alpha-4</version>
</dependency>
</dependencies>
<distributionManagement>
<repository>
<id>empirerepo</id>
<name>Empire Repository at floogle.net</name>
<url>scp://floogle.net/empirerepo</url>
</repository>
<site>
<id>empirewebsite</id>
<url>scp://floogle.net/www/floogle/empire</url>
</site>
</distributionManagement>
</project>
And the generated release.properties file is:
#release configuration
#Mon May 15 16:58:15 PDT 2006
preparationGoals=clean integration-test
scm.tagBase=svn\://floogle.net/empire/JEC.tags
scm.tag=JEC-2.0.0-alpha-7
project.dev.com.empireclassic\:JEC=2.0.0-alpha-8-SNAPSHOT
exec.additionalArguments=-P Snapshots
completedPhase=map-development-versions
project.rel.com.empireclassic\:JEC=2.0.0-alpha-7
scm.url=scm\:svn\:svn\://floogle.net/empire/JEC
Any ideas?
Chas Douglass
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Release Failure
Posted by ben short <be...@benshort.co.uk>.
All,
I got the null pointer so I checked out the sourcecode and had a look.
Its because you havent specified a connection element in your scm
element.
Eg:
<scm>
<connection>scm:svn:svn://floogle.net/empire/JEC.tags/JEC-2.0.0-alpha-7</connection>
<developerConnection>scm:svn:svn://floogle.net/empire/JEC.tags/JEC-2.0.0-alpha-7</developerConnection>
</scm>
With this in my build works with maven-release-plugin 2.0-beta-4.
Ben
On 5/25/06, Jakub Pawlowicz <co...@jakubpawlowicz.com> wrote:
> Hi Andrew,
>
> I'm using the latest version available on ibiblio - ie 2.0-beta-4.
> I'll try to use beta-3 and beta-5-SNAPSHOT, and post some feedback here.
>
> Regards,
> Jakub
>
> On Wed, 24 May 2006 16:21:27 -0700, Andrew Kreps wrote
> > What version of the release plugin are you using? I found that I had
> > less trouble when specifying the 2.0-beta-4 version rather than
> > 2.0-beta-5-SNAPSHOT.
> >
> > On 5/24/06, Jakub Pawlowicz <co...@jakubpawlowicz.com> wrote:
> > > Hi everyone,
> > >
> > > I'm facing the same problem with my project.
> > > Have anybody solved this problem by now?
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Release Failure [SOLVED]
Posted by Kenney Westerhof <ke...@apache.org>.
Hi,
The NPE is definitely a bug.
But <connection> IS mandatory, and <developerConnection> isn't.
DeveloperConnection is meant to be an override for connection, if
the developer URL (write access) is different from the URL for read-only
access. So normally you'd only specify the <connection>.
Btw, this issue seems fixed now in SVN.
-- Kenney
shinsato wrote:
> This may or not be a bug in the code (though I think the nullpointerexception
> is clearly a bug from a user perspective - the failure should be more
> informative - I've submitted a bug about it in JIRA, MRELEASE-167).
>
> But if it isn't a bug, it should be more clearly described in the online
> documentation. This was an unnecessary waste of several hours, and I can
> see from the other posts to the nabble forum, I wasn't the first. I'll
> submit a JIRA issue about this.
>
> Cheers,
> Harold
>
>
>
> Hi,
>
> I've found the reason why release:prepare fails for my project (it's
> an issue from Chas Douglass' post).
> The scm section of my pom.xml was like this:
> <scm>
> <developerConnection>scm:svn:file:///usr/local/svnrep/xxx/trunk</
> developerConnection>
> </scm>
>
> I downloaded the release plugin sources and checked the write method
> in the PropertiesReleaseConfigurationStore.java class (this is where
> the process fails).
> And I've found, that the method assumes that a <connection> tag is
> mandatory inside the scm section.
> So the (temporary?) solution to this problem is to include both, the
> <connection> and <developerConnection> in the scm section, eg:
> <scm>
> <connection>scm:svn:file:///usr/local/svnrep/xxx/trunk</connection>
> <developerConnection>scm:svn:file:///usr/local/svnrep/xxx/trunk</
> developerConnection>
> </scm>
>
> I think that this is a bug. The <developerConnection> should be
> mandatory, but <connection> should be optional, because the
> <developerConnection> is needed to perform
> the release:perform. Or at least the process should stop and an
> apropriate message should send to console.
> If it's a bug, I will file a JIRA issue and send a patch.
> What do you think?
>
> Regards,
> Jakub
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Release Failure [SOLVED]
Posted by shinsato <ha...@shinsato.com>.
This may or not be a bug in the code (though I think the nullpointerexception
is clearly a bug from a user perspective - the failure should be more
informative - I've submitted a bug about it in JIRA, MRELEASE-167).
But if it isn't a bug, it should be more clearly described in the online
documentation. This was an unnecessary waste of several hours, and I can
see from the other posts to the nabble forum, I wasn't the first. I'll
submit a JIRA issue about this.
Cheers,
Harold
Hi,
I've found the reason why release:prepare fails for my project (it's
an issue from Chas Douglass' post).
The scm section of my pom.xml was like this:
<scm>
<developerConnection>scm:svn:file:///usr/local/svnrep/xxx/trunk</
developerConnection>
</scm>
I downloaded the release plugin sources and checked the write method
in the PropertiesReleaseConfigurationStore.java class (this is where
the process fails).
And I've found, that the method assumes that a <connection> tag is
mandatory inside the scm section.
So the (temporary?) solution to this problem is to include both, the
<connection> and <developerConnection> in the scm section, eg:
<scm>
<connection>scm:svn:file:///usr/local/svnrep/xxx/trunk</connection>
<developerConnection>scm:svn:file:///usr/local/svnrep/xxx/trunk</
developerConnection>
</scm>
I think that this is a bug. The <developerConnection> should be
mandatory, but <connection> should be optional, because the
<developerConnection> is needed to perform
the release:perform. Or at least the process should stop and an
apropriate message should send to console.
If it's a bug, I will file a JIRA issue and send a patch.
What do you think?
Regards,
Jakub
--
View this message in context: http://www.nabble.com/Release-Failure-tf1624778.html#a6574232
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Release Failure [SOLVED]
Posted by Jakub Pawlowicz <co...@jakubpawlowicz.com>.
Hi,
I've found the reason why release:prepare fails for my project (it's
an issue from Chas Douglass' post).
The scm section of my pom.xml was like this:
<scm>
<developerConnection>scm:svn:file:///usr/local/svnrep/xxx/trunk</
developerConnection>
</scm>
I downloaded the release plugin sources and checked the write method
in the PropertiesReleaseConfigurationStore.java class (this is where
the process fails).
And I've found, that the method assumes that a <connection> tag is
mandatory inside the scm section.
So the (temporary?) solution to this problem is to include both, the
<connection> and <developerConnection> in the scm section, eg:
<scm>
<connection>scm:svn:file:///usr/local/svnrep/xxx/trunk</connection>
<developerConnection>scm:svn:file:///usr/local/svnrep/xxx/trunk</
developerConnection>
</scm>
I think that this is a bug. The <developerConnection> should be
mandatory, but <connection> should be optional, because the
<developerConnection> is needed to perform
the release:perform. Or at least the process should stop and an
apropriate message should send to console.
If it's a bug, I will file a JIRA issue and send a patch.
What do you think?
Regards,
Jakub
On May 25, 2006, at 7:56 AM, Jakub Pawlowicz wrote:
> Hi Andrew,
>
> I'm using the latest version available on ibiblio - ie 2.0-beta-4.
> I'll try to use beta-3 and beta-5-SNAPSHOT, and post some feedback
> here.
>
> Regards,
> Jakub
>
> On Wed, 24 May 2006 16:21:27 -0700, Andrew Kreps wrote
>> What version of the release plugin are you using? I found that I had
>> less trouble when specifying the 2.0-beta-4 version rather than
>> 2.0-beta-5-SNAPSHOT.
>>
>> On 5/24/06, Jakub Pawlowicz <co...@jakubpawlowicz.com> wrote:
>>> Hi everyone,
>>>
>>> I'm facing the same problem with my project.
>>> Have anybody solved this problem by now?
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Release Failure
Posted by Jakub Pawlowicz <co...@jakubpawlowicz.com>.
Hi Andrew,
I'm using the latest version available on ibiblio - ie 2.0-beta-4.
I'll try to use beta-3 and beta-5-SNAPSHOT, and post some feedback here.
Regards,
Jakub
On Wed, 24 May 2006 16:21:27 -0700, Andrew Kreps wrote
> What version of the release plugin are you using? I found that I had
> less trouble when specifying the 2.0-beta-4 version rather than
> 2.0-beta-5-SNAPSHOT.
>
> On 5/24/06, Jakub Pawlowicz <co...@jakubpawlowicz.com> wrote:
> > Hi everyone,
> >
> > I'm facing the same problem with my project.
> > Have anybody solved this problem by now?
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Release Failure
Posted by Andrew Kreps <an...@gmail.com>.
What version of the release plugin are you using? I found that I had
less trouble when specifying the 2.0-beta-4 version rather than
2.0-beta-5-SNAPSHOT.
On 5/24/06, Jakub Pawlowicz <co...@jakubpawlowicz.com> wrote:
> Hi everyone,
>
> I'm facing the same problem with my project.
> Have anybody solved this problem by now?
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Release Failure
Posted by Jakub Pawlowicz <co...@jakubpawlowicz.com>.
Hi everyone,
I'm facing the same problem with my project.
Have anybody solved this problem by now?
Regards,
Jakub
On May 16, 2006, at 2:22 AM, Chas Douglass wrote:
> I was successfully using "mvn release:prepare" on Friday. After
> the upgrades and problems over the weekend I'm assuming something
> changed (although it could be something I changed, of course).
>
> When I execute it now I get a failure:
>
> [INFO]
> ----------------------------------------------------------------------
> --
> [ERROR] FATAL ERROR
> [INFO]
> ----------------------------------------------------------------------
> --
> [INFO] null
> [INFO]
> ----------------------------------------------------------------------
> --
> [INFO] Trace
> java.lang.NullPointerException
> at java.util.Hashtable.put(Hashtable.java:396)
> at java.util.Properties.setProperty(Properties.java:128)
> at
> org.apache.maven.plugins.release.config.PropertiesReleaseConfiguration
> Store.write(PropertiesReleaseConfigurationStore.java:225)
> at
> org.apache.maven.plugins.release.config.PropertiesReleaseConfiguration
> Store.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.executeStandaloneG
> oal(DefaultLifecycleExecutor.java:488)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal
> (DefaultLifecycleExecutor.java:458)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHand
> leFailures(DefaultLifecycleExecutor.java:306)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegment
> s(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)
>
> (The full output can be seen at http://www.floogle.net/JEC/
> catch.release.prepare)
>
> The pom is:
> <project xmlns="http://maven.apache.org/POM/4.0.0"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://
> maven.apache.org/maven-v4_0_0.xsd">
> <modelVersion>4.0.0</modelVersion>
> <groupId>com.empireclassic</groupId>
> <artifactId>JEC</artifactId>
> <name>Java Empire Client</name>
> <version>2.0.0-alpha-7</version>
> <description>The GUI client for classic Empire</description>
> <scm>
> <developerConnection>scm:svn:svn://floogle.net/empire/JEC.tags/
> JEC-2.0.0-alpha-7</developerConnection>
> </scm>
> <build>
> <resources>
> <resource>
> <filtering>true</filtering>
> <directory>src/main/resources</directory>
> <excludes>
> <exclude>image/**</exclude>
> </excludes>
> </resource>
> <resource>
> <directory>src/main/resources</directory>
> <includes>
> <include>image/**</include>
> </includes>
> </resource>
> </resources>
> <plugins>
> <plugin>
> <artifactId>maven-compiler-plugin</artifactId>
> <configuration>
> <source>1.5</source>
> <target>1.5</target>
> </configuration>
> </plugin>
> <plugin>
> <artifactId>maven-release-plugin</artifactId>
> <configuration>
> <tagBase>svn://floogle.net/empire/JEC.tags</tagBase>
> </configuration>
> </plugin>
> <plugin>
> <artifactId>maven-jar-plugin</artifactId>
> <configuration>
> <archive>
> <manifestEntries>
> <Class-Path>.</Class-Path>
> </manifestEntries>
> <manifest>
> <packageName>com.empireclassic.jec</packageName>
> <mainClass>com.empireclassic.jec.JEC</mainClass>
> </manifest>
> </archive>
> </configuration>
> </plugin>
> </plugins>
> </build>
> <repositories>
> <repository>
> <id>empirerepo</id>
> <url>http://empire.floogle.net/empirerepo</url>
> </repository>
> </repositories>
> <dependencies>
> <dependency>
> <groupId>piccolo</groupId>
> <artifactId>piccolo</artifactId>
> <version>1.2</version>
> </dependency>
> <dependency>
> <groupId>piccolo</groupId>
> <artifactId>piccolox</artifactId>
> <version>1.2</version>
> </dependency>
> <dependency>
> <groupId>com.empireclassic</groupId>
> <artifactId>RemoteEmpire</artifactId>
> <version>1.0-alpha-4</version>
> </dependency>
> </dependencies>
> <distributionManagement>
> <repository>
> <id>empirerepo</id>
> <name>Empire Repository at floogle.net</name>
> <url>scp://floogle.net/empirerepo</url>
> </repository>
> <site>
> <id>empirewebsite</id>
> <url>scp://floogle.net/www/floogle/empire</url>
> </site>
> </distributionManagement>
> </project>
>
> And the generated release.properties file is:
> #release configuration
> #Mon May 15 16:58:15 PDT 2006
> preparationGoals=clean integration-test
> scm.tagBase=svn\://floogle.net/empire/JEC.tags
> scm.tag=JEC-2.0.0-alpha-7
> project.dev.com.empireclassic\:JEC=2.0.0-alpha-8-SNAPSHOT
> exec.additionalArguments=-P Snapshots
> completedPhase=map-development-versions
> project.rel.com.empireclassic\:JEC=2.0.0-alpha-7
> scm.url=scm\:svn\:svn\://floogle.net/empire/JEC
>
> Any ideas?
>
> Chas Douglass
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org