I also discovered the release:branch goal. Don't know how I missed that
one, previously. That made the job quite quick and painless.
Thanks again!
Brian E. Fox wrote:
Yep, it's similar to what is described here:
http://www.sonatype.com/people/2009/01/best-practices-for-releasing-with
-3rd-party-snapshot-dependencies/
-----Original Message-----
From: Todd Thiessen [mailto:thies...@nortel.com]
Sent: Friday, April 03, 2009 1:31 PM
To: Maven Users List
Subject: RE: Help with patching a release?
If you don't own the project, it is a bit more involved. In that case
you would have to export the project and then import it to your svn repo
and then update the scm and distribution management sections
accordingly. Also remember to change the version of the project to
distinguish it from the next "proper" release of the actual project. So,
for example, if the current version is:
2.1-SNAPSHOT
Give it a version like:
2.1-dave-1-SNAPSHOT
sSo that you don't collide with the next official release.
---
Todd Thiessen
-----Original Message-----
From: Brian E. Fox [mailto:bri...@reply.infinity.nu]
Sent: Friday, April 03, 2009 1:16 PM
To: Maven Users List
Subject: RE: Help with patching a release?
Easiest thing is to roll the poms to a snapshot and then do a
traditional release. This assumes that the project you are
patching is your own and the scm info is correct.
-----Original Message-----
From: David C. Hicks [mailto:dhi...@i-hicks.org]
Sent: Friday, April 03, 2009 12:32 PM
To: Maven Users
Subject: Help with patching a release?
Hi gang,
I need to apply a small patch to a project that has already
been released. In general, I understand that I need to
branch the tag under which the code was released, make the
change, then create a new release. I'm running into a
problem, I guess with the release plugin, though. (I'm sure
it's *my* problem, not the plugin's.) When I try to run a
release:prepare, I get an error indicating that I don't have
a SNAPSHOT project. OK, that makes sense, because I branched
from a release tag. So, my question is, what would be the
proper procedure for
this exercise? I mean, from the point of view of Maven and
maven-release-plugin, how should I go about the steps of
applying a change to a released version?
This is the first time I've had to do this. So, it's a
learning opportunity.
Thanks,
Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
