You are viewing a plain text version of this content. The canonical link for it is here.
Posted to announce@maven.apache.org by Olivier Lamy <ol...@apache.org> on 2009/03/28 18:36:36 UTC
[ANN] Maven Release Plugin 2.0-beta-9 Released
Hi,
The Maven team is pleased to announce the release of the Maven Release
Plugin, version 2.0-beta-9.
http://maven.apache.org/plugins/maven-release-plugin/
You should specify the version in your project's plugin configuration:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-release-plugin</artifactId>
<version>2.0-beta-9</version>
</plugin>
Release Notes - Maven 2.x Release Plugin - Version 2.0-beta-9
** Bug
* [MRELEASE-273] - Regression: NullPointerException at end of
standalone "release:perform"
* [MRELEASE-375] - release plugin does not work with subversion > 1.5.0
* [MRELEASE-379] - return results after performing a release
* [MRELEASE-381] - url syntax not good enough for the git scm provider
* [MRELEASE-386] - Sneaky bug in DefaultReleaseManager.perform()
* [MRELEASE-393] - NoSuchMethodError when using
InvokerMavenExecutor with cmd line arg "--quiet"
* [MRELEASE-405] - Wrong branch-name parameter
** Improvement
* [MRELEASE-385] - Upgrade to last scm version (1.2)
* [MRELEASE-392] - Align release-parent, release-manager and
release-plugin versions
* [MRELEASE-427] - Add a mojo parameter for using the new remote
tagging for svn scm provider (to prevent issue with svn > 1.5.0)
* [MRELEASE-429] - Support for a [token]-SNAPSHOT in addition to
[number]-SNAPSHOT
** Task
* [MRELEASE-390] - Add VSS dependency
Have Fun!
--
The Maven Team
Re: [ANN] Maven Release Plugin 2.0-beta-9 Released
Posted by Stephen Connolly <st...@gmail.com>.
Unless you write a pre-commit hook to ban 1.6 clients
afaik, you can use a 1.1 client with a 1.6 server and a 1.6 client with a
1.1 server (put it may only be officially supported as far back as 1.4)
-Stephen
2009/4/2 Stephen Connolly <st...@gmail.com>
> Yes
>
>
> 2009/4/1 Todd Thiessen <th...@nortel.com>
>
>> Consider your response acknowledged ;-).
>>
>> We may be moving to 1.6 soon (on the server side). Would a 1.6 client
>> work with a 1.5 server?
>>
>> ---
>> Todd Thiessen
>>
>>
>> > -----Original Message-----
>> > From: Stephen Connolly [mailto:stephen.alan.connolly@gmail.com]
>> > Sent: Wednesday, April 01, 2009 4:53 PM
>> > To: Maven Users List
>> > Subject: Re: [ANN] Maven Release Plugin 2.0-beta-9 Released
>> >
>> > Has anybody tried switching from neon to serf as the
>> > repository access method???
>> >
>> > I read on the svn list that 1.5.1+ WC->URL tagging for
>> > http/https repositories works with serf but not neon
>> >
>> > I have not been able to try this yet as it would mean
>> > recompiling my client.
>> >
>> > This is a client only setting and does not affect the server.
>> >
>> > the 1.6.0 binaries from collabnet include both serf and neon
>> > transports and you can switch between them using one of the
>> > config files.
>> >
>> > tagging works with svn, and ssh+svn repos no problem
>> >
>> > (I keep saying this because nobody seems to be acknowedging
>> > me saying this
>> > ;-) )
>> >
>> > -Stephen
>> >
>> > 2009/4/1 Todd Thiessen <th...@nortel.com>
>> >
>> > >
>> > > > > The part where it says how to make a complex tag. ie:
>> > making a tag
>> > > > > from a working copy.
>> > > >
>> > > > A complex tag refers to ways of making a "snapshot" of a specific
>> > > > working copy, quoting specifically "which is an exact snapshot of
>> > > > your working copy-mixed revisions, URLs, and all".
>> > >
>> > > Which is precisely what a complex tag is.
>> > >
>> > > > Trying to make a release from such a "snapshot" is a fundamental
>> > > > contradiction in terms in the maven world, and very bad practice.
>> > >
>> > > This is what the maven plugin does (ie: create a tag from
>> > your working
>> > > copy), so I am not sure how you can say it is a bad practice in the
>> > > maven world. You will have to take that up with the maven world I
>> > > suppose ;-).
>> > >
>> > >
>> > ---------------------------------------------------------------------
>> > > 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: [ANN] Maven Release Plugin 2.0-beta-9 Released
Posted by Stephen Connolly <st...@gmail.com>.
Yes
2009/4/1 Todd Thiessen <th...@nortel.com>
> Consider your response acknowledged ;-).
>
> We may be moving to 1.6 soon (on the server side). Would a 1.6 client
> work with a 1.5 server?
>
> ---
> Todd Thiessen
>
>
> > -----Original Message-----
> > From: Stephen Connolly [mailto:stephen.alan.connolly@gmail.com]
> > Sent: Wednesday, April 01, 2009 4:53 PM
> > To: Maven Users List
> > Subject: Re: [ANN] Maven Release Plugin 2.0-beta-9 Released
> >
> > Has anybody tried switching from neon to serf as the
> > repository access method???
> >
> > I read on the svn list that 1.5.1+ WC->URL tagging for
> > http/https repositories works with serf but not neon
> >
> > I have not been able to try this yet as it would mean
> > recompiling my client.
> >
> > This is a client only setting and does not affect the server.
> >
> > the 1.6.0 binaries from collabnet include both serf and neon
> > transports and you can switch between them using one of the
> > config files.
> >
> > tagging works with svn, and ssh+svn repos no problem
> >
> > (I keep saying this because nobody seems to be acknowedging
> > me saying this
> > ;-) )
> >
> > -Stephen
> >
> > 2009/4/1 Todd Thiessen <th...@nortel.com>
> >
> > >
> > > > > The part where it says how to make a complex tag. ie:
> > making a tag
> > > > > from a working copy.
> > > >
> > > > A complex tag refers to ways of making a "snapshot" of a specific
> > > > working copy, quoting specifically "which is an exact snapshot of
> > > > your working copy-mixed revisions, URLs, and all".
> > >
> > > Which is precisely what a complex tag is.
> > >
> > > > Trying to make a release from such a "snapshot" is a fundamental
> > > > contradiction in terms in the maven world, and very bad practice.
> > >
> > > This is what the maven plugin does (ie: create a tag from
> > your working
> > > copy), so I am not sure how you can say it is a bad practice in the
> > > maven world. You will have to take that up with the maven world I
> > > suppose ;-).
> > >
> > >
> > ---------------------------------------------------------------------
> > > 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: [ANN] Maven Release Plugin 2.0-beta-9 Released
Posted by Todd Thiessen <th...@nortel.com>.
Consider your response acknowledged ;-).
We may be moving to 1.6 soon (on the server side). Would a 1.6 client
work with a 1.5 server?
---
Todd Thiessen
> -----Original Message-----
> From: Stephen Connolly [mailto:stephen.alan.connolly@gmail.com]
> Sent: Wednesday, April 01, 2009 4:53 PM
> To: Maven Users List
> Subject: Re: [ANN] Maven Release Plugin 2.0-beta-9 Released
>
> Has anybody tried switching from neon to serf as the
> repository access method???
>
> I read on the svn list that 1.5.1+ WC->URL tagging for
> http/https repositories works with serf but not neon
>
> I have not been able to try this yet as it would mean
> recompiling my client.
>
> This is a client only setting and does not affect the server.
>
> the 1.6.0 binaries from collabnet include both serf and neon
> transports and you can switch between them using one of the
> config files.
>
> tagging works with svn, and ssh+svn repos no problem
>
> (I keep saying this because nobody seems to be acknowedging
> me saying this
> ;-) )
>
> -Stephen
>
> 2009/4/1 Todd Thiessen <th...@nortel.com>
>
> >
> > > > The part where it says how to make a complex tag. ie:
> making a tag
> > > > from a working copy.
> > >
> > > A complex tag refers to ways of making a "snapshot" of a specific
> > > working copy, quoting specifically "which is an exact snapshot of
> > > your working copy-mixed revisions, URLs, and all".
> >
> > Which is precisely what a complex tag is.
> >
> > > Trying to make a release from such a "snapshot" is a fundamental
> > > contradiction in terms in the maven world, and very bad practice.
> >
> > This is what the maven plugin does (ie: create a tag from
> your working
> > copy), so I am not sure how you can say it is a bad practice in the
> > maven world. You will have to take that up with the maven world I
> > suppose ;-).
> >
> >
> ---------------------------------------------------------------------
> > 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: [ANN] Maven Release Plugin 2.0-beta-9 Released
Posted by Stephen Connolly <st...@gmail.com>.
Has anybody tried switching from neon to serf as the repository access
method???
I read on the svn list that 1.5.1+ WC->URL tagging for http/https
repositories works with serf but not neon
I have not been able to try this yet as it would mean recompiling my client.
This is a client only setting and does not affect the server.
the 1.6.0 binaries from collabnet include both serf and neon transports and
you can switch between them using one of the config files.
tagging works with svn, and ssh+svn repos no problem
(I keep saying this because nobody seems to be acknowedging me saying this
;-) )
-Stephen
2009/4/1 Todd Thiessen <th...@nortel.com>
>
> > > The part where it says how to make a complex tag. ie: making a tag
> > > from a working copy.
> >
> > A complex tag refers to ways of making a "snapshot" of a
> > specific working copy, quoting specifically "which is an
> > exact snapshot of your working copy-mixed revisions, URLs, and all".
>
> Which is precisely what a complex tag is.
>
> > Trying to make a release from such a "snapshot" is a
> > fundamental contradiction in terms in the maven world, and
> > very bad practice.
>
> This is what the maven plugin does (ie: create a tag from your working
> copy), so I am not sure how you can say it is a bad practice in the
> maven world. You will have to take that up with the maven world I
> suppose ;-).
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
RE: [ANN] Maven Release Plugin 2.0-beta-9 Released
Posted by Todd Thiessen <th...@nortel.com>.
> > The part where it says how to make a complex tag. ie: making a tag
> > from a working copy.
>
> A complex tag refers to ways of making a "snapshot" of a
> specific working copy, quoting specifically "which is an
> exact snapshot of your working copy-mixed revisions, URLs, and all".
Which is precisely what a complex tag is.
> Trying to make a release from such a "snapshot" is a
> fundamental contradiction in terms in the maven world, and
> very bad practice.
This is what the maven plugin does (ie: create a tag from your working
copy), so I am not sure how you can say it is a bad practice in the
maven world. You will have to take that up with the maven world I
suppose ;-).
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [ANN] Maven Release Plugin 2.0-beta-9 Released
Posted by Graham Leggett <mi...@sharp.fm>.
Todd Thiessen wrote:
> The part where it says how to make a complex tag. ie: making a tag from
> a working copy.
A complex tag refers to ways of making a "snapshot" of a specific
working copy, quoting specifically "which is an exact snapshot of your
working copy—mixed revisions, URLs, and all".
Trying to make a release from such a "snapshot" is a fundamental
contradiction in terms in the maven world, and very bad practice.
Regards,
Graham
--
RE: [ANN] Maven Release Plugin 2.0-beta-9 Released
Posted by Todd Thiessen <th...@nortel.com>.
The part where it says how to make a complex tag. ie: making a tag from
a working copy.
---
Todd Thiessen
> -----Original Message-----
> From: Graham Leggett [mailto:minfrin@sharp.fm]
> Sent: Wednesday, April 01, 2009 12:10 PM
> To: Maven Users List
> Subject: Re: [ANN] Maven Release Plugin 2.0-beta-9 Released
>
> Todd Thiessen wrote:
>
> > Not according to svn.
> >
> > http://svnbook.red-bean.com/en/1.1/ch04s06.html
>
> That's the docs for tags, which part of those docs are you
> referring to specifically?
>
> Regards,
> Graham
> --
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [ANN] Maven Release Plugin 2.0-beta-9 Released
Posted by Graham Leggett <mi...@sharp.fm>.
Todd Thiessen wrote:
> Not according to svn.
>
> http://svnbook.red-bean.com/en/1.1/ch04s06.html
That's the docs for tags, which part of those docs are you referring to
specifically?
Regards,
Graham
--
RE: [ANN] Maven Release Plugin 2.0-beta-9 Released
Posted by Todd Thiessen <th...@nortel.com>.
Not according to svn.
http://svnbook.red-bean.com/en/1.1/ch04s06.html
---
Todd Thiessen
> -----Original Message-----
> From: Graham Leggett [mailto:minfrin@sharp.fm]
> Sent: Wednesday, April 01, 2009 10:58 AM
> To: Maven Users List
> Subject: Re: [ANN] Maven Release Plugin 2.0-beta-9 Released
>
> Todd Thiessen wrote:
>
> > Yes you can. See svn documentation:
> >
> > http://svnbook.red-bean.com/en/1.0/re07.html
> >
> > In particular, the WC -> URL case.
>
> You've posted the docs for the svn "copy" command, a "tag"
> only formally exists when you use the URL -> URL case.
>
> In the case of the WC->URL case, as I read it, it is simply a
> shorthand way of saying "add" followed by "commit" of a
> single file. The docs don't clarify whether any history is
> kept, or whether any requirement exists for the WC file to be
> checked in or up to date first.
>
> A tag without history isn't a tag.
>
> Regards,
> Graham
> --
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [ANN] Maven Release Plugin 2.0-beta-9 Released
Posted by Graham Leggett <mi...@sharp.fm>.
Todd Thiessen wrote:
> Yes you can. See svn documentation:
>
> http://svnbook.red-bean.com/en/1.0/re07.html
>
> In particular, the WC -> URL case.
You've posted the docs for the svn "copy" command, a "tag" only formally
exists when you use the URL -> URL case.
In the case of the WC->URL case, as I read it, it is simply a shorthand
way of saying "add" followed by "commit" of a single file. The docs
don't clarify whether any history is kept, or whether any requirement
exists for the WC file to be checked in or up to date first.
A tag without history isn't a tag.
Regards,
Graham
--
RE: [ANN] Maven Release Plugin 2.0-beta-9 Released
Posted by Todd Thiessen <th...@nortel.com>.
Yes you can. See svn documentation:
http://svnbook.red-bean.com/en/1.0/re07.html
In particular, the WC -> URL case.
---
Todd Thiessen
> -----Original Message-----
> From: Graham Leggett [mailto:minfrin@sharp.fm]
> Sent: Wednesday, April 01, 2009 10:47 AM
> To: Maven Users List
> Subject: Re: [ANN] Maven Release Plugin 2.0-beta-9 Released
>
> Todd Thiessen wrote:
>
> > So if I understand remote tagging correctly, this means
> that a tag is
> > taken
> > off the trunk, not the working copy.
>
> You can't (to my knowledge) tag a working copy, that doesn't
> make any sense. Can you clarify?
>
> Regards,
> Graham
> --
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [ANN] Maven Release Plugin 2.0-beta-9 Released
Posted by Graham Leggett <mi...@sharp.fm>.
Todd Thiessen wrote:
> So if I understand remote tagging correctly, this means that a tag is taken
> off the trunk, not the working copy.
You can't (to my knowledge) tag a working copy, that doesn't make any
sense. Can you clarify?
Regards,
Graham
--
RE: [ANN] Maven Release Plugin 2.0-beta-9 Released
Posted by Todd Thiessen <th...@nortel.com>.
Agreed. And keep some pressure on the svn community to fix the issue. I think it has gone under the svn radar for a while because of workarounds like this. I have not interfaced with the svn community myself so I am not practicing what I am preaching ;-).
---
Todd Thiessen
> -----Original Message-----
> From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
> Sent: Wednesday, April 01, 2009 10:22 AM
> To: Maven Users List
> Subject: RE: [ANN] Maven Release Plugin 2.0-beta-9 Released
>
> I agree completely, but until/unless the svn team fixes this
> major defect, there's not much we can do. (besides switch
> everyone to git ;-) )
>
> -----Original Message-----
> From: Todd Thiessen [mailto:thiessen@nortel.com]
> Sent: Wednesday, April 01, 2009 10:18 AM
> To: Maven Users List
> Subject: RE: [ANN] Maven Release Plugin 2.0-beta-9 Released
>
> I was pleased when I heard that there was a fix for the tags
> not working with svn in 1.5.1 bug [1]. I didn't look into the
> solution in great detail at first and I apologize for that.
> It is little difficult to look at everything all the time as
> I am sure you all are familiar with. I did take a little time
> this morning to understand the solution however. I never did
> understand what "remoteTagging" meant for an option in the
> release plugin (which needs to be documented, btw, on the
> release plugin site).
>
> So if I understand remote tagging correctly, this means that
> a tag is taken off the trunk, not the working copy.
>
> Doesn't this break backwards compatibility? For instance if
> there are users out there who do rely on making a tag of the
> working copy to ensure that you don't tag something committed
> during a build, once they upgrade to release 9 of the release
> plugin, this won't work for them anymore.
>
> I view the remoteTaggins option as a work around. It is
> fundamentally a bug in svn (it did work in pre 1.5.1, and
> doing an svn copy of a working copy is documented to work
> [2]). If svn ever fixes it, then the remoteTagging option
> wouldn't be needed anymore and should be defaulted to false.
>
> I understand the comments in [3] which indicate that the
> likelihood of a commit occurring during a build isn't the
> common case, but how can you tell? This could happen more
> than we might think and there are tags of releases out there
> which do not match the built artifacts. There is no way to
> know without doing a detailed analysis of the artifacts and
> the tagged source. I feel it is pretty safe to say that such
> an analysis hasn't been done ;-). Even if someone did happen
> to stumble upon such a case where they were stepping through
> the source in there debugger and noticed that lines didn't
> match up. It may be dismissed if the lines were "close
> enough" to follow or simply upgrading to a more recent
> version of the artifact all of a sudden fixes it.
>
> Ultimately I feel we still need an svn solution to this.
> Remote tagging is only a work around.
>
> My 2 cents anyway.
>
> [1] http://jira.codehaus.org/browse/SCM-406
> [2] http://svnbook.red-bean.com/en/1.0/re07.html
> [3] http://jira.codehaus.org/browse/SCM-262
>
> ---
> Todd Thiessen
>
>
> > -----Original Message-----
> > From: oliver.lamy@gmail.com [mailto:oliver.lamy@gmail.com]
> On Behalf
> > Of Olivier Lamy
> > Sent: Wednesday, April 01, 2009 6:54 AM
> > To: Maven Users List
> > Subject: Re: [ANN] Maven Release Plugin 2.0-beta-9 Released
> >
> > 2009/4/1 Jorg Heymans <jo...@gmail.com>:
> > > (taking this back to the users list)
> > >
> > > On Wed, Apr 1, 2009 at 10:01 AM, Olivier Lamy
> > <ol...@apache.org> wrote:
> > >> 2009/4/1 Jorg Heymans <jo...@gmail.com>:
> > >>> On Wed, Apr 1, 2009 at 9:33 AM, Olivier Lamy
> > <ol...@apache.org> wrote:
> > >>>
> > >>>> Try mvn help:effective-pom I'm not sure the scm
> > information is correct.
> > >>>
> > >>> I don't know what to make from the scm info, in any case
> > it points
> > >>> to a non-existing tag:
> > >>>
> > >>> <scm>
> > >>>
> > >>>
> > <connection>scm:svn:http://server/svn/project/tags/myparent-4/myproj
> > >>> ect</connection>
> > >>>
> > >>>
> > <developerConnection>scm:svn:http://server/svn/project/tags/myparent
> > >>> -4/myproject</developerConnection>
> > >>> </scm>
> > >>>
> > >>> The "myproject" at the end seems bad. In any case somehow
> > beta-8 was
> > >>> able to cope with this, wierd.
> > >>
> > >> :-) (in this case IMHO your project is bad : publishing
> site will
> > >> publish bad source info etc.. changelog plugin can not
> work etc..)
> > >
> > > The released parent pom contains this scm element :
> > >
> > > <scm>
> > >
> > >
> >
> <connection>scm:svn:http://server/svn/project/tags/myparent-4</connect
> > > ion>
> > >
> > >
> >
> <developerConnection>scm:svn:http://server/svn/project/tags/myparent-4
> > > </developerConnection>
> > > </scm>
> > >
> > > Do you mean this is wrong ?
> > No the release parent has correct information but not your child(s)
> > pom(s) because if the child doesn't have any scm
> information they are
> > inherited from the parent ! + your current project's artifactId
> >
> > in your case effective pom will be :
> > <scm>
> >
> > <connection>scm:svn:http://server/svn/project/tags/myparent-4/
> > ${artifactId}</connection>
> >
> > <developerConnection>scm:svn:http://server/svn/project/tags/my
> > parent-4/${artifactId}</developerConnection>
> > </scm>
> >
> > And IMHO this is not correct for your current project !
> > SIte informations won't be correct.
> > Your child poms must contains their own scm informations (something
> > like) :
> >
> > <scm>
> >
> > <connection>scm:svn:http://server/svn/project/myparent/trunk/$
> {artifactId}</connection>
> >
> > <developerConnection>scm:svn:http://server/svn/project/myparen
> > t/trunk/${artifactId}</developerConnection>
> > </scm>
> >
> > Sure it's a side effect of using remote tagging to have a
> workaround
> > on the svn > 1.5.0 issue.
> > But you can set remoteTagging to false in the release plugin
> > configuration.
> > >
> > > Thanks,
> > > Jorg
> > >
> > >
> >
> ---------------------------------------------------------------------
> > > 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
>
>
> ---------------------------------------------------------------------
> 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: [ANN] Maven Release Plugin 2.0-beta-9 Released
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
I agree completely, but until/unless the svn team fixes this major defect, there's not much we can do. (besides switch everyone to git ;-) )
-----Original Message-----
From: Todd Thiessen [mailto:thiessen@nortel.com]
Sent: Wednesday, April 01, 2009 10:18 AM
To: Maven Users List
Subject: RE: [ANN] Maven Release Plugin 2.0-beta-9 Released
I was pleased when I heard that there was a fix for the tags not working with svn in 1.5.1 bug [1]. I didn't look into the solution in great detail at first and I apologize for that. It is little difficult to look at everything all the time as I am sure you all are familiar with. I did take a little time this morning to understand the solution however. I never did understand what "remoteTagging" meant for an option in the release plugin (which needs to be documented, btw, on the release plugin site).
So if I understand remote tagging correctly, this means that a tag is taken off the trunk, not the working copy.
Doesn't this break backwards compatibility? For instance if there are users out there who do rely on making a tag of the working copy to ensure that you don't tag something committed during a build, once they upgrade to release 9 of the release plugin, this won't work for them anymore.
I view the remoteTaggins option as a work around. It is fundamentally a bug in svn (it did work in pre 1.5.1, and doing an svn copy of a working copy is documented to work [2]). If svn ever fixes it, then the remoteTagging option wouldn't be needed anymore and should be defaulted to false.
I understand the comments in [3] which indicate that the likelihood of a commit occurring during a build isn't the common case, but how can you tell? This could happen more than we might think and there are tags of releases out there which do not match the built artifacts. There is no way to know without doing a detailed analysis of the artifacts and the tagged source. I feel it is pretty safe to say that such an analysis hasn't been done ;-). Even if someone did happen to stumble upon such a case where they were stepping through the source in there debugger and noticed that lines didn't match up. It may be dismissed if the lines were "close enough" to follow or simply upgrading to a more recent version of the artifact all of a sudden fixes it.
Ultimately I feel we still need an svn solution to this. Remote tagging is only a work around.
My 2 cents anyway.
[1] http://jira.codehaus.org/browse/SCM-406
[2] http://svnbook.red-bean.com/en/1.0/re07.html
[3] http://jira.codehaus.org/browse/SCM-262
---
Todd Thiessen
> -----Original Message-----
> From: oliver.lamy@gmail.com [mailto:oliver.lamy@gmail.com] On
> Behalf Of Olivier Lamy
> Sent: Wednesday, April 01, 2009 6:54 AM
> To: Maven Users List
> Subject: Re: [ANN] Maven Release Plugin 2.0-beta-9 Released
>
> 2009/4/1 Jorg Heymans <jo...@gmail.com>:
> > (taking this back to the users list)
> >
> > On Wed, Apr 1, 2009 at 10:01 AM, Olivier Lamy
> <ol...@apache.org> wrote:
> >> 2009/4/1 Jorg Heymans <jo...@gmail.com>:
> >>> On Wed, Apr 1, 2009 at 9:33 AM, Olivier Lamy
> <ol...@apache.org> wrote:
> >>>
> >>>> Try mvn help:effective-pom I'm not sure the scm
> information is correct.
> >>>
> >>> I don't know what to make from the scm info, in any case
> it points
> >>> to a non-existing tag:
> >>>
> >>> <scm>
> >>>
> >>>
> <connection>scm:svn:http://server/svn/project/tags/myparent-4/myproj
> >>> ect</connection>
> >>>
> >>>
> <developerConnection>scm:svn:http://server/svn/project/tags/myparent
> >>> -4/myproject</developerConnection>
> >>> </scm>
> >>>
> >>> The "myproject" at the end seems bad. In any case somehow
> beta-8 was
> >>> able to cope with this, wierd.
> >>
> >> :-) (in this case IMHO your project is bad : publishing site will
> >> publish bad source info etc.. changelog plugin can not work etc..)
> >
> > The released parent pom contains this scm element :
> >
> > <scm>
> >
> >
> <connection>scm:svn:http://server/svn/project/tags/myparent-4</connect
> > ion>
> >
> >
> <developerConnection>scm:svn:http://server/svn/project/tags/myparent-4
> > </developerConnection>
> > </scm>
> >
> > Do you mean this is wrong ?
> No the release parent has correct information but not your child(s)
> pom(s) because if the child doesn't have any scm information
> they are inherited from the parent ! + your current project's
> artifactId
>
> in your case effective pom will be :
> <scm>
>
> <connection>scm:svn:http://server/svn/project/tags/myparent-4/
> ${artifactId}</connection>
>
> <developerConnection>scm:svn:http://server/svn/project/tags/my
> parent-4/${artifactId}</developerConnection>
> </scm>
>
> And IMHO this is not correct for your current project !
> SIte informations won't be correct.
> Your child poms must contains their own scm informations
> (something like) :
>
> <scm>
>
> <connection>scm:svn:http://server/svn/project/myparent/trunk/$
{artifactId}</connection>
>
> <developerConnection>scm:svn:http://server/svn/project/myparen
> t/trunk/${artifactId}</developerConnection>
> </scm>
>
> Sure it's a side effect of using remote tagging to have a
> workaround on the svn > 1.5.0 issue.
> But you can set remoteTagging to false in the release plugin
> configuration.
> >
> > Thanks,
> > Jorg
> >
> >
> ---------------------------------------------------------------------
> > 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
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: [ANN] Maven Release Plugin 2.0-beta-9 Released
Posted by Todd Thiessen <th...@nortel.com>.
I was pleased when I heard that there was a fix for the tags not working with svn in 1.5.1 bug [1]. I didn't look into the solution in great detail at first and I apologize for that. It is little difficult to look at everything all the time as I am sure you all are familiar with. I did take a little time this morning to understand the solution however. I never did understand what "remoteTagging" meant for an option in the release plugin (which needs to be documented, btw, on the release plugin site).
So if I understand remote tagging correctly, this means that a tag is taken off the trunk, not the working copy.
Doesn't this break backwards compatibility? For instance if there are users out there who do rely on making a tag of the working copy to ensure that you don't tag something committed during a build, once they upgrade to release 9 of the release plugin, this won't work for them anymore.
I view the remoteTaggins option as a work around. It is fundamentally a bug in svn (it did work in pre 1.5.1, and doing an svn copy of a working copy is documented to work [2]). If svn ever fixes it, then the remoteTagging option wouldn't be needed anymore and should be defaulted to false.
I understand the comments in [3] which indicate that the likelihood of a commit occurring during a build isn't the common case, but how can you tell? This could happen more than we might think and there are tags of releases out there which do not match the built artifacts. There is no way to know without doing a detailed analysis of the artifacts and the tagged source. I feel it is pretty safe to say that such an analysis hasn't been done ;-). Even if someone did happen to stumble upon such a case where they were stepping through the source in there debugger and noticed that lines didn't match up. It may be dismissed if the lines were "close enough" to follow or simply upgrading to a more recent version of the artifact all of a sudden fixes it.
Ultimately I feel we still need an svn solution to this. Remote tagging is only a work around.
My 2 cents anyway.
[1] http://jira.codehaus.org/browse/SCM-406
[2] http://svnbook.red-bean.com/en/1.0/re07.html
[3] http://jira.codehaus.org/browse/SCM-262
---
Todd Thiessen
> -----Original Message-----
> From: oliver.lamy@gmail.com [mailto:oliver.lamy@gmail.com] On
> Behalf Of Olivier Lamy
> Sent: Wednesday, April 01, 2009 6:54 AM
> To: Maven Users List
> Subject: Re: [ANN] Maven Release Plugin 2.0-beta-9 Released
>
> 2009/4/1 Jorg Heymans <jo...@gmail.com>:
> > (taking this back to the users list)
> >
> > On Wed, Apr 1, 2009 at 10:01 AM, Olivier Lamy
> <ol...@apache.org> wrote:
> >> 2009/4/1 Jorg Heymans <jo...@gmail.com>:
> >>> On Wed, Apr 1, 2009 at 9:33 AM, Olivier Lamy
> <ol...@apache.org> wrote:
> >>>
> >>>> Try mvn help:effective-pom I'm not sure the scm
> information is correct.
> >>>
> >>> I don't know what to make from the scm info, in any case
> it points
> >>> to a non-existing tag:
> >>>
> >>> <scm>
> >>>
> >>>
> <connection>scm:svn:http://server/svn/project/tags/myparent-4/myproj
> >>> ect</connection>
> >>>
> >>>
> <developerConnection>scm:svn:http://server/svn/project/tags/myparent
> >>> -4/myproject</developerConnection>
> >>> </scm>
> >>>
> >>> The "myproject" at the end seems bad. In any case somehow
> beta-8 was
> >>> able to cope with this, wierd.
> >>
> >> :-) (in this case IMHO your project is bad : publishing site will
> >> publish bad source info etc.. changelog plugin can not work etc..)
> >
> > The released parent pom contains this scm element :
> >
> > <scm>
> >
> >
> <connection>scm:svn:http://server/svn/project/tags/myparent-4</connect
> > ion>
> >
> >
> <developerConnection>scm:svn:http://server/svn/project/tags/myparent-4
> > </developerConnection>
> > </scm>
> >
> > Do you mean this is wrong ?
> No the release parent has correct information but not your child(s)
> pom(s) because if the child doesn't have any scm information
> they are inherited from the parent ! + your current project's
> artifactId
>
> in your case effective pom will be :
> <scm>
>
> <connection>scm:svn:http://server/svn/project/tags/myparent-4/
> ${artifactId}</connection>
>
> <developerConnection>scm:svn:http://server/svn/project/tags/my
> parent-4/${artifactId}</developerConnection>
> </scm>
>
> And IMHO this is not correct for your current project !
> SIte informations won't be correct.
> Your child poms must contains their own scm informations
> (something like) :
>
> <scm>
>
> <connection>scm:svn:http://server/svn/project/myparent/trunk/$
{artifactId}</connection>
>
> <developerConnection>scm:svn:http://server/svn/project/myparen
> t/trunk/${artifactId}</developerConnection>
> </scm>
>
> Sure it's a side effect of using remote tagging to have a
> workaround on the svn > 1.5.0 issue.
> But you can set remoteTagging to false in the release plugin
> configuration.
> >
> > Thanks,
> > Jorg
> >
> >
> ---------------------------------------------------------------------
> > 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: [ANN] Maven Release Plugin 2.0-beta-9 Released
Posted by Daniel Kulp <dk...@apache.org>.
On Wed April 1 2009 11:16:58 am Jochen Wiedmann wrote:
> On Wed, Apr 1, 2009 at 1:23 PM, Mark Hobson <ma...@gmail.com> wrote:
> > 2009/4/1 Olivier Lamy <ol...@apache.org>:
> >> No the release parent has correct information but not your child(s)
> >> pom(s) because if the child doesn't have any scm information they are
> >> inherited from the parent ! + your current project's artifactId
> >
> > Are there any plans to change this for Maven 2.x/3.x? It's quite an
> > assumption to make that a project's SCM location is directly beneath
> > its parent.
>
> It's the only reasonable assumption for a default value. So, why change it?
No. If everything is being released as a reactor build, there are at LEAST
two better options for a "default" value:
1) If the <parent> element in the pom has a "relativePath" element in it, that
could be used to resolve the current location against the parent.
2) If the parent is in the reactor, you can get the "basedir" for the parent
and the "basedir" for the child and calculate the difference from an scm
standpoint.
Either of those would yield much better results (IMO) than the "blindly assume
parent+artifactId" thing that is there now.
--
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [ANN] Maven Release Plugin 2.0-beta-9 Released
Posted by Jochen Wiedmann <jo...@gmail.com>.
On Wed, Apr 1, 2009 at 1:23 PM, Mark Hobson <ma...@gmail.com> wrote:
> 2009/4/1 Olivier Lamy <ol...@apache.org>:
>> No the release parent has correct information but not your child(s)
>> pom(s) because if the child doesn't have any scm information they are
>> inherited from the parent ! + your current project's artifactId
>
> Are there any plans to change this for Maven 2.x/3.x? It's quite an
> assumption to make that a project's SCM location is directly beneath
> its parent.
It's the only reasonable assumption for a default value. So, why change it?
--
I have always wished for my computer to be as easy to use as my
telephone; my wish has come true because I can no longer figure out
how to use my telephone.
-- (Bjarne Stroustrup,
http://www.research.att.com/~bs/bs_faq.html#really-say-that
My guess: Nokia E50)
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [ANN] Maven Release Plugin 2.0-beta-9 Released
Posted by Mark Hobson <ma...@gmail.com>.
2009/4/1 Olivier Lamy <ol...@apache.org>:
> No the release parent has correct information but not your child(s)
> pom(s) because if the child doesn't have any scm information they are
> inherited from the parent ! + your current project's artifactId
Are there any plans to change this for Maven 2.x/3.x? It's quite an
assumption to make that a project's SCM location is directly beneath
its parent.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [ANN] Maven Release Plugin 2.0-beta-9 Released
Posted by Olivier Lamy <ol...@apache.org>.
2009/4/1 Jorg Heymans <jo...@gmail.com>:
> (taking this back to the users list)
>
> On Wed, Apr 1, 2009 at 10:01 AM, Olivier Lamy <ol...@apache.org> wrote:
>> 2009/4/1 Jorg Heymans <jo...@gmail.com>:
>>> On Wed, Apr 1, 2009 at 9:33 AM, Olivier Lamy <ol...@apache.org> wrote:
>>>
>>>> Try mvn help:effective-pom I'm not sure the scm information is correct.
>>>
>>> I don't know what to make from the scm info, in any case it points to
>>> a non-existing tag:
>>>
>>> <scm>
>>> <connection>scm:svn:http://server/svn/project/tags/myparent-4/myproject</connection>
>>> <developerConnection>scm:svn:http://server/svn/project/tags/myparent-4/myproject</developerConnection>
>>> </scm>
>>>
>>> The "myproject" at the end seems bad. In any case somehow beta-8 was
>>> able to cope with this, wierd.
>>
>> :-) (in this case IMHO your project is bad : publishing site will
>> publish bad source info etc.. changelog plugin can not work etc..)
>
> The released parent pom contains this scm element :
>
> <scm>
> <connection>scm:svn:http://server/svn/project/tags/myparent-4</connection>
> <developerConnection>scm:svn:http://server/svn/project/tags/myparent-4</developerConnection>
> </scm>
>
> Do you mean this is wrong ?
No the release parent has correct information but not your child(s)
pom(s) because if the child doesn't have any scm information they are
inherited from the parent ! + your current project's artifactId
in your case effective pom will be :
<scm>
<connection>scm:svn:http://server/svn/project/tags/myparent-4/${artifactId}</connection>
<developerConnection>scm:svn:http://server/svn/project/tags/myparent-4/${artifactId}</developerConnection>
</scm>
And IMHO this is not correct for your current project !
SIte informations won't be correct.
Your child poms must contains their own scm informations (something like) :
<scm>
<connection>scm:svn:http://server/svn/project/myparent/trunk/${artifactId}</connection>
<developerConnection>scm:svn:http://server/svn/project/myparent/trunk/${artifactId}</developerConnection>
</scm>
Sure it's a side effect of using remote tagging to have a workaround
on the svn > 1.5.0 issue.
But you can set remoteTagging to false in the release plugin configuration.
>
> Thanks,
> Jorg
>
> ---------------------------------------------------------------------
> 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: [ANN] Maven Release Plugin 2.0-beta-9 Released
Posted by Jorg Heymans <jo...@gmail.com>.
(taking this back to the users list)
On Wed, Apr 1, 2009 at 10:01 AM, Olivier Lamy <ol...@apache.org> wrote:
> 2009/4/1 Jorg Heymans <jo...@gmail.com>:
>> On Wed, Apr 1, 2009 at 9:33 AM, Olivier Lamy <ol...@apache.org> wrote:
>>
>>> Try mvn help:effective-pom I'm not sure the scm information is correct.
>>
>> I don't know what to make from the scm info, in any case it points to
>> a non-existing tag:
>>
>> <scm>
>> <connection>scm:svn:http://server/svn/project/tags/myparent-4/myproject</connection>
>> <developerConnection>scm:svn:http://server/svn/project/tags/myparent-4/myproject</developerConnection>
>> </scm>
>>
>> The "myproject" at the end seems bad. In any case somehow beta-8 was
>> able to cope with this, wierd.
>
> :-) (in this case IMHO your project is bad : publishing site will
> publish bad source info etc.. changelog plugin can not work etc..)
The released parent pom contains this scm element :
<scm>
<connection>scm:svn:http://server/svn/project/tags/myparent-4</connection>
<developerConnection>scm:svn:http://server/svn/project/tags/myparent-4</developerConnection>
</scm>
Do you mean this is wrong ?
Thanks,
Jorg
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [ANN] Maven Release Plugin 2.0-beta-9 Released
Posted by Olivier Lamy <ol...@apache.org>.
2009/4/1 Jorg Heymans <jo...@gmail.com>:
> On Wed, Apr 1, 2009 at 9:33 AM, Olivier Lamy <ol...@apache.org> wrote:
>
>> Try mvn help:effective-pom I'm not sure the scm information is correct.
>
> I don't know what to make from the scm info, in any case it points to
> a non-existing tag:
>
> <scm>
> <connection>scm:svn:http://server/svn/project/tags/myparent-4/myproject</connection>
> <developerConnection>scm:svn:http://server/svn/project/tags/myparent-4/myproject</developerConnection>
> </scm>
>
> The "myproject" at the end seems bad. In any case somehow beta-8 was
> able to cope with this, wierd.
:-) (in this case IMHO your project is bad : publishing site will
publish bad source info etc.. changelog plugin can not work etc..)
>
>>
>> btw : can you test with
>> http://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.html#remoteTagging
>> set to false ?
>
> yep, added -DremoteTagging=false and now it works.
>
> Should i file an issue for this ?
Uhm not really sure because it's configurable ( default value to true
is intentionnal [1] ) and it work if scm element is correctly
configured :-)
[1] http://jira.codehaus.org/browse/MRELEASE-427
>
> Thanks,
> Jorg
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [ANN] Maven Release Plugin 2.0-beta-9 Released
Posted by Jorg Heymans <jo...@gmail.com>.
On Wed, Apr 1, 2009 at 9:33 AM, Olivier Lamy <ol...@apache.org> wrote:
> Try mvn help:effective-pom I'm not sure the scm information is correct.
I don't know what to make from the scm info, in any case it points to
a non-existing tag:
<scm>
<connection>scm:svn:http://server/svn/project/tags/myparent-4/myproject</connection>
<developerConnection>scm:svn:http://server/svn/project/tags/myparent-4/myproject</developerConnection>
</scm>
The "myproject" at the end seems bad. In any case somehow beta-8 was
able to cope with this, wierd.
>
> btw : can you test with
> http://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.html#remoteTagging
> set to false ?
yep, added -DremoteTagging=false and now it works.
Should i file an issue for this ?
Thanks,
Jorg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [ANN] Maven Release Plugin 2.0-beta-9 Released
Posted by Olivier Lamy <ol...@apache.org>.
2009/4/1 Jorg Heymans <jo...@gmail.com>:
> On Wed, Apr 1, 2009 at 9:24 AM, Olivier Lamy <ol...@apache.org> wrote:
>> Hi,
>> Is it a release of a project which doesn't have a scm element and use
>> a released parent project which has one ?
>>
>
> That's the exact situation yes. Is this no longer an accepted
> situation perhaps ?
It looks not (or not really tested :-) ) because here you have a bad
information in your pom.
Try mvn help:effective-pom I'm not sure the scm information is correct.
btw : can you test with
http://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.html#remoteTagging
set to false ?
>
> Jorg
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [ANN] Maven Release Plugin 2.0-beta-9 Released
Posted by Jorg Heymans <jo...@gmail.com>.
On Wed, Apr 1, 2009 at 9:24 AM, Olivier Lamy <ol...@apache.org> wrote:
> Hi,
> Is it a release of a project which doesn't have a scm element and use
> a released parent project which has one ?
>
That's the exact situation yes. Is this no longer an accepted
situation perhaps ?
Jorg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [ANN] Maven Release Plugin 2.0-beta-9 Released
Posted by Olivier Lamy <ol...@apache.org>.
Hi,
Is it a release of a project which doesn't have a scm element and use
a released parent project which has one ?
--
Olivier
2009/4/1 Jorg Heymans <jo...@gmail.com>:
> Hi,
>
> beta-9 seems to have introduced something which my project cannot
> grok. I'm trying to do a release of my project's main pom:
>
> $mvn release:prepare -N -Darguments=-N
> ....
> ....
> [INFO] ------------------------------------------------------------------------
> [ERROR] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Unable to tag SCM
> Provider message:
> The svn tag command failed.
> Command output:
> svn: Path 'http://server/svn/project/tags/myparent-4/myproject' does
> not exist in revision 8100
>
> I reverted to beta-8 and it's fine again. Is there any output i should
> provide to help troubleshoot this ?
>
> Thanks,
> Jorg
>
>
>
> On Sun, Mar 29, 2009 at 1:40 AM, Niall Pemberton
> <ni...@gmail.com> wrote:
>> On Sat, Mar 28, 2009 at 10:53 PM, Brian E. Fox <br...@reply.infinity.nu> wrote:
>>> All set.
>>
>> Thanks
>>
>> Niall
>>
>>
>>> -----Original Message-----
>>> From: Niall Pemberton [mailto:niall.pemberton@gmail.com]
>>> Sent: Saturday, March 28, 2009 5:52 PM
>>> To: Maven Developers List
>>> Subject: Re: [ANN] Maven Release Plugin 2.0-beta-9 Released
>>>
>>> The parent pom doesn't seem to have found its way to the public repo
>>> yet, is it on its way?
>>>
>>> http://repo1.maven.org/maven2/org/apache/maven/release/maven-release/
>>>
>>> Niall
>>>
>>> On Sat, Mar 28, 2009 at 5:36 PM, Olivier Lamy <ol...@apache.org> wrote:
>>>> Hi,
>>>> The Maven team is pleased to announce the release of the Maven Release
>>>> Plugin, version 2.0-beta-9.
>>>>
>>>> http://maven.apache.org/plugins/maven-release-plugin/
>>>>
>>>> You should specify the version in your project's plugin configuration:
>>>>
>>>> <plugin>
>>>> <groupId>org.apache.maven.plugins</groupId>
>>>> <artifactId>maven-release-plugin</artifactId>
>>>> <version>2.0-beta-9</version>
>>>> </plugin>
>>>>
>>>>
>>>> Release Notes - Maven 2.x Release Plugin - Version 2.0-beta-9
>>>>
>>>>
>>>> ** Bug
>>>> * [MRELEASE-273] - Regression: NullPointerException at end of
>>>> standalone "release:perform"
>>>> * [MRELEASE-375] - release plugin does not work with subversion > 1.5.0
>>>> * [MRELEASE-379] - return results after performing a release
>>>> * [MRELEASE-381] - url syntax not good enough for the git scm provider
>>>> * [MRELEASE-386] - Sneaky bug in DefaultReleaseManager.perform()
>>>> * [MRELEASE-393] - NoSuchMethodError when using
>>>> InvokerMavenExecutor with cmd line arg "--quiet"
>>>> * [MRELEASE-405] - Wrong branch-name parameter
>>>>
>>>> ** Improvement
>>>> * [MRELEASE-385] - Upgrade to last scm version (1.2)
>>>> * [MRELEASE-392] - Align release-parent, release-manager and
>>>> release-plugin versions
>>>> * [MRELEASE-427] - Add a mojo parameter for using the new remote
>>>> tagging for svn scm provider (to prevent issue with svn > 1.5.0)
>>>> * [MRELEASE-429] - Support for a [token]-SNAPSHOT in addition to
>>>> [number]-SNAPSHOT
>>>>
>>>>
>>>> ** Task
>>>> * [MRELEASE-390] - Add VSS dependency
>>>>
>>>> Have Fun!
>>>>
>>>> --
>>>> The Maven Team
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [ANN] Maven Release Plugin 2.0-beta-9 Released
Posted by Jorg Heymans <jo...@gmail.com>.
Hi,
beta-9 seems to have introduced something which my project cannot
grok. I'm trying to do a release of my project's main pom:
$mvn release:prepare -N -Darguments=-N
....
....
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Unable to tag SCM
Provider message:
The svn tag command failed.
Command output:
svn: Path 'http://server/svn/project/tags/myparent-4/myproject' does
not exist in revision 8100
I reverted to beta-8 and it's fine again. Is there any output i should
provide to help troubleshoot this ?
Thanks,
Jorg
On Sun, Mar 29, 2009 at 1:40 AM, Niall Pemberton
<ni...@gmail.com> wrote:
> On Sat, Mar 28, 2009 at 10:53 PM, Brian E. Fox <br...@reply.infinity.nu> wrote:
>> All set.
>
> Thanks
>
> Niall
>
>
>> -----Original Message-----
>> From: Niall Pemberton [mailto:niall.pemberton@gmail.com]
>> Sent: Saturday, March 28, 2009 5:52 PM
>> To: Maven Developers List
>> Subject: Re: [ANN] Maven Release Plugin 2.0-beta-9 Released
>>
>> The parent pom doesn't seem to have found its way to the public repo
>> yet, is it on its way?
>>
>> http://repo1.maven.org/maven2/org/apache/maven/release/maven-release/
>>
>> Niall
>>
>> On Sat, Mar 28, 2009 at 5:36 PM, Olivier Lamy <ol...@apache.org> wrote:
>>> Hi,
>>> The Maven team is pleased to announce the release of the Maven Release
>>> Plugin, version 2.0-beta-9.
>>>
>>> http://maven.apache.org/plugins/maven-release-plugin/
>>>
>>> You should specify the version in your project's plugin configuration:
>>>
>>> <plugin>
>>> <groupId>org.apache.maven.plugins</groupId>
>>> <artifactId>maven-release-plugin</artifactId>
>>> <version>2.0-beta-9</version>
>>> </plugin>
>>>
>>>
>>> Release Notes - Maven 2.x Release Plugin - Version 2.0-beta-9
>>>
>>>
>>> ** Bug
>>> * [MRELEASE-273] - Regression: NullPointerException at end of
>>> standalone "release:perform"
>>> * [MRELEASE-375] - release plugin does not work with subversion > 1.5.0
>>> * [MRELEASE-379] - return results after performing a release
>>> * [MRELEASE-381] - url syntax not good enough for the git scm provider
>>> * [MRELEASE-386] - Sneaky bug in DefaultReleaseManager.perform()
>>> * [MRELEASE-393] - NoSuchMethodError when using
>>> InvokerMavenExecutor with cmd line arg "--quiet"
>>> * [MRELEASE-405] - Wrong branch-name parameter
>>>
>>> ** Improvement
>>> * [MRELEASE-385] - Upgrade to last scm version (1.2)
>>> * [MRELEASE-392] - Align release-parent, release-manager and
>>> release-plugin versions
>>> * [MRELEASE-427] - Add a mojo parameter for using the new remote
>>> tagging for svn scm provider (to prevent issue with svn > 1.5.0)
>>> * [MRELEASE-429] - Support for a [token]-SNAPSHOT in addition to
>>> [number]-SNAPSHOT
>>>
>>>
>>> ** Task
>>> * [MRELEASE-390] - Add VSS dependency
>>>
>>> Have Fun!
>>>
>>> --
>>> The Maven Team
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [ANN] Maven Release Plugin 2.0-beta-9 Released
Posted by Niall Pemberton <ni...@gmail.com>.
On Sat, Mar 28, 2009 at 10:53 PM, Brian E. Fox <br...@reply.infinity.nu> wrote:
> All set.
Thanks
Niall
> -----Original Message-----
> From: Niall Pemberton [mailto:niall.pemberton@gmail.com]
> Sent: Saturday, March 28, 2009 5:52 PM
> To: Maven Developers List
> Subject: Re: [ANN] Maven Release Plugin 2.0-beta-9 Released
>
> The parent pom doesn't seem to have found its way to the public repo
> yet, is it on its way?
>
> http://repo1.maven.org/maven2/org/apache/maven/release/maven-release/
>
> Niall
>
> On Sat, Mar 28, 2009 at 5:36 PM, Olivier Lamy <ol...@apache.org> wrote:
>> Hi,
>> The Maven team is pleased to announce the release of the Maven Release
>> Plugin, version 2.0-beta-9.
>>
>> http://maven.apache.org/plugins/maven-release-plugin/
>>
>> You should specify the version in your project's plugin configuration:
>>
>> <plugin>
>> <groupId>org.apache.maven.plugins</groupId>
>> <artifactId>maven-release-plugin</artifactId>
>> <version>2.0-beta-9</version>
>> </plugin>
>>
>>
>> Release Notes - Maven 2.x Release Plugin - Version 2.0-beta-9
>>
>>
>> ** Bug
>> * [MRELEASE-273] - Regression: NullPointerException at end of
>> standalone "release:perform"
>> * [MRELEASE-375] - release plugin does not work with subversion > 1.5.0
>> * [MRELEASE-379] - return results after performing a release
>> * [MRELEASE-381] - url syntax not good enough for the git scm provider
>> * [MRELEASE-386] - Sneaky bug in DefaultReleaseManager.perform()
>> * [MRELEASE-393] - NoSuchMethodError when using
>> InvokerMavenExecutor with cmd line arg "--quiet"
>> * [MRELEASE-405] - Wrong branch-name parameter
>>
>> ** Improvement
>> * [MRELEASE-385] - Upgrade to last scm version (1.2)
>> * [MRELEASE-392] - Align release-parent, release-manager and
>> release-plugin versions
>> * [MRELEASE-427] - Add a mojo parameter for using the new remote
>> tagging for svn scm provider (to prevent issue with svn > 1.5.0)
>> * [MRELEASE-429] - Support for a [token]-SNAPSHOT in addition to
>> [number]-SNAPSHOT
>>
>>
>> ** Task
>> * [MRELEASE-390] - Add VSS dependency
>>
>> Have Fun!
>>
>> --
>> The Maven Team
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: [ANN] Maven Release Plugin 2.0-beta-9 Released
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
All set.
-----Original Message-----
From: Niall Pemberton [mailto:niall.pemberton@gmail.com]
Sent: Saturday, March 28, 2009 5:52 PM
To: Maven Developers List
Subject: Re: [ANN] Maven Release Plugin 2.0-beta-9 Released
The parent pom doesn't seem to have found its way to the public repo
yet, is it on its way?
http://repo1.maven.org/maven2/org/apache/maven/release/maven-release/
Niall
On Sat, Mar 28, 2009 at 5:36 PM, Olivier Lamy <ol...@apache.org> wrote:
> Hi,
> The Maven team is pleased to announce the release of the Maven Release
> Plugin, version 2.0-beta-9.
>
> http://maven.apache.org/plugins/maven-release-plugin/
>
> You should specify the version in your project's plugin configuration:
>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-release-plugin</artifactId>
> <version>2.0-beta-9</version>
> </plugin>
>
>
> Release Notes - Maven 2.x Release Plugin - Version 2.0-beta-9
>
>
> ** Bug
> * [MRELEASE-273] - Regression: NullPointerException at end of
> standalone "release:perform"
> * [MRELEASE-375] - release plugin does not work with subversion > 1.5.0
> * [MRELEASE-379] - return results after performing a release
> * [MRELEASE-381] - url syntax not good enough for the git scm provider
> * [MRELEASE-386] - Sneaky bug in DefaultReleaseManager.perform()
> * [MRELEASE-393] - NoSuchMethodError when using
> InvokerMavenExecutor with cmd line arg "--quiet"
> * [MRELEASE-405] - Wrong branch-name parameter
>
> ** Improvement
> * [MRELEASE-385] - Upgrade to last scm version (1.2)
> * [MRELEASE-392] - Align release-parent, release-manager and
> release-plugin versions
> * [MRELEASE-427] - Add a mojo parameter for using the new remote
> tagging for svn scm provider (to prevent issue with svn > 1.5.0)
> * [MRELEASE-429] - Support for a [token]-SNAPSHOT in addition to
> [number]-SNAPSHOT
>
>
> ** Task
> * [MRELEASE-390] - Add VSS dependency
>
> Have Fun!
>
> --
> The Maven Team
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [ANN] Maven Release Plugin 2.0-beta-9 Released
Posted by Niall Pemberton <ni...@gmail.com>.
The parent pom doesn't seem to have found its way to the public repo
yet, is it on its way?
http://repo1.maven.org/maven2/org/apache/maven/release/maven-release/
Niall
On Sat, Mar 28, 2009 at 5:36 PM, Olivier Lamy <ol...@apache.org> wrote:
> Hi,
> The Maven team is pleased to announce the release of the Maven Release
> Plugin, version 2.0-beta-9.
>
> http://maven.apache.org/plugins/maven-release-plugin/
>
> You should specify the version in your project's plugin configuration:
>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-release-plugin</artifactId>
> <version>2.0-beta-9</version>
> </plugin>
>
>
> Release Notes - Maven 2.x Release Plugin - Version 2.0-beta-9
>
>
> ** Bug
> * [MRELEASE-273] - Regression: NullPointerException at end of
> standalone "release:perform"
> * [MRELEASE-375] - release plugin does not work with subversion > 1.5.0
> * [MRELEASE-379] - return results after performing a release
> * [MRELEASE-381] - url syntax not good enough for the git scm provider
> * [MRELEASE-386] - Sneaky bug in DefaultReleaseManager.perform()
> * [MRELEASE-393] - NoSuchMethodError when using
> InvokerMavenExecutor with cmd line arg "--quiet"
> * [MRELEASE-405] - Wrong branch-name parameter
>
> ** Improvement
> * [MRELEASE-385] - Upgrade to last scm version (1.2)
> * [MRELEASE-392] - Align release-parent, release-manager and
> release-plugin versions
> * [MRELEASE-427] - Add a mojo parameter for using the new remote
> tagging for svn scm provider (to prevent issue with svn > 1.5.0)
> * [MRELEASE-429] - Support for a [token]-SNAPSHOT in addition to
> [number]-SNAPSHOT
>
>
> ** Task
> * [MRELEASE-390] - Add VSS dependency
>
> Have Fun!
>
> --
> The Maven Team
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: The skin does not exist: Unable to determine the release version
Posted by Martin Gainty <mg...@hotmail.com>.
version is indeterminant
what happens if you follow instructions to d/l the requested skin and install with known
group-id,version and artifact-id
?
Martin
______________________________________________
Disclaimer and confidentiality note
This message is confidential and may be privileged. If you are not the intended recipient, we kindly ask you to please inform the sender. Any unauthorised dissemination or copying hereof is prohibited. This message serves for information purposes only and shall not have any legally binding effect. Given that e-mails can easily be subject to manipulation, we can not accept any liability for the content provided.
> To: users@maven.apache.org
> Subject: The skin does not exist: Unable to determine the release version
> From: jerry.thome@hewitt.com
> Date: Mon, 30 Mar 2009 20:27:05 -0500
>
> Sorry if I missed this as a recent posting. Last night, several of my
> Maven projects running in Hudson starting to fail with the same error
> message. Does the recent "site" plug-in release have anything to do with
> this?
>
> It's becoming problematic to delete files in a repo and have maven
> auto-download them, which seems to fix this problem.
>
> Thanks.
>
>
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] The skin does not exist: Unable to determine the release version
>
> Try downloading the file manually from the project website.
>
> Then, install it using the command:
> mvn install:install-file -DgroupId=org.apache.maven.skins
> -DartifactId=maven-default-skin -Dversion=RELEASE -Dpackaging=jar
> -Dfile=/path/to/file
>
> Alternatively, if you host your own repository you can deploy the file
> there:
> mvn deploy:deploy-file -DgroupId=org.apache.maven.skins
> -DartifactId=maven-default-skin -Dversion=RELEASE -Dpackaging=jar
> -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
>
>
> org.apache.maven.skins:maven-default-skin:jar:RELEASE
>
>
>
>
>
>
> The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by e-mail.
>
>
_________________________________________________________________
Express your personality in color! Preview and select themes for Hotmail®.
http://www.windowslive-hotmail.com/LearnMore/personalize.aspx?ocid=TXT_MSGTX_WL_HM_express_032009#colortheme
Re: The skin does not exist: Unable to determine the release
version
Posted by Jerry Thome <je...@hewitt.com>.
That fixed it. I'll be sure to do that first in the future.
Thank you.
"Siegfried Goeschl" <si...@it20one.at>
03/31/2009 05:15 AM
Please respond to
"Maven Users List" <us...@maven.apache.org>, siegfried.goeschl@it20one.at
To
"Maven Users List" <us...@maven.apache.org>
cc
Subject
Re: The skin does not exist: Unable to determine the release version
Hi Jerry,
the bad news are that I had the same problem - the good news are that I
was able to get rid of the problem
E.g. run "mvn -U site" to force an update of your repo - thanks to Wendy
Smoak helping me with this issue ...
Cheers,
Siegfried Goeschl
Jerry Thome wrote:
> Sorry if I missed this as a recent posting. Last night, several of my
> Maven projects running in Hudson starting to fail with the same error
> message. Does the recent "site" plug-in release have anything to do
with
> this?
>
> It's becoming problematic to delete files in a repo and have maven
> auto-download them, which seems to fix this problem.
>
> Thanks.
>
>
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] The skin does not exist: Unable to determine the release version
>
> Try downloading the file manually from the project website.
>
> Then, install it using the command:
> mvn install:install-file -DgroupId=org.apache.maven.skins
> -DartifactId=maven-default-skin -Dversion=RELEASE -Dpackaging=jar
> -Dfile=/path/to/file
>
> Alternatively, if you host your own repository you can deploy the file
> there:
> mvn deploy:deploy-file -DgroupId=org.apache.maven.skins
> -DartifactId=maven-default-skin -Dversion=RELEASE -Dpackaging=jar
> -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
>
>
> org.apache.maven.skins:maven-default-skin:jar:RELEASE
>
>
>
>
>
>
> The information contained in this e-mail and any accompanying documents
may contain information that is confidential or otherwise protected from
disclosure. If you are not the intended recipient of this message, or if
this message has been addressed to you in error, please immediately alert
the sender by reply e-mail and then delete this message, including any
attachments. Any dissemination, distribution or other use of the contents
of this message by anyone other than the intended recipient is strictly
prohibited. All messages sent to and from this e-mail address may be
monitored as permitted by applicable law and regulations to ensure
compliance with our internal policies and to protect our business. E-mails
are not secure and cannot be guaranteed to be error free as they can be
intercepted, amended, lost or destroyed, or contain viruses. You are
deemed to have accepted these risks if you communicate with us by e-mail.
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by e-mail.
Re: The skin does not exist: Unable to determine the release version
Posted by Siegfried Goeschl <si...@it20one.at>.
Hi Jerry,
the bad news are that I had the same problem - the good news are that I
was able to get rid of the problem
E.g. run "mvn -U site" to force an update of your repo - thanks to Wendy
Smoak helping me with this issue ...
Cheers,
Siegfried Goeschl
Jerry Thome wrote:
> Sorry if I missed this as a recent posting. Last night, several of my
> Maven projects running in Hudson starting to fail with the same error
> message. Does the recent "site" plug-in release have anything to do with
> this?
>
> It's becoming problematic to delete files in a repo and have maven
> auto-download them, which seems to fix this problem.
>
> Thanks.
>
>
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] The skin does not exist: Unable to determine the release version
>
> Try downloading the file manually from the project website.
>
> Then, install it using the command:
> mvn install:install-file -DgroupId=org.apache.maven.skins
> -DartifactId=maven-default-skin -Dversion=RELEASE -Dpackaging=jar
> -Dfile=/path/to/file
>
> Alternatively, if you host your own repository you can deploy the file
> there:
> mvn deploy:deploy-file -DgroupId=org.apache.maven.skins
> -DartifactId=maven-default-skin -Dversion=RELEASE -Dpackaging=jar
> -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
>
>
> org.apache.maven.skins:maven-default-skin:jar:RELEASE
>
>
>
>
>
>
> The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by e-mail.
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
The skin does not exist: Unable to determine the release
version
Posted by Jerry Thome <je...@hewitt.com>.
Sorry if I missed this as a recent posting. Last night, several of my
Maven projects running in Hudson starting to fail with the same error
message. Does the recent "site" plug-in release have anything to do with
this?
It's becoming problematic to delete files in a repo and have maven
auto-download them, which seems to fix this problem.
Thanks.
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] The skin does not exist: Unable to determine the release version
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.apache.maven.skins
-DartifactId=maven-default-skin -Dversion=RELEASE -Dpackaging=jar
-Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file
there:
mvn deploy:deploy-file -DgroupId=org.apache.maven.skins
-DartifactId=maven-default-skin -Dversion=RELEASE -Dpackaging=jar
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
org.apache.maven.skins:maven-default-skin:jar:RELEASE
The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by e-mail.