You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Jakub Pawlowicz <co...@jakubpawlowicz.com> on 2006/05/25 20:10:17 UTC
Re: Release Failure [SOLVED]
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 [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