You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by "David C. Hicks" <dh...@i-hicks.org> on 2009/04/03 18:32:14 UTC
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-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Help with patching a release?
Posted by "David C. Hicks" <dh...@i-hicks.org>.
I had assumed that it would probably involve some manual steps to get
the version tags set up correctly. I do own the project, so that's not a
problem. I just didn't want to waste time editing pom settings if there
were a more "automagic" way to handle.
Thanks to both of you!
Dave
Todd Thiessen wrote:
> 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:brianf@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:dhicks@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-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: Help with patching a release?
Posted by "David C. Hicks" <dh...@i-hicks.org>.
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:thiessen@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:brianf@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:dhicks@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-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: Help with patching a release?
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
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:thiessen@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:brianf@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:dhicks@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-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
Visiting non-standard Signature object
Posted by Jerry Thome <je...@hewitt.com>.
In the last couple of weeks, we started seeing the below messages during
the dependency report generation of site. I see a hundred or so of these
messages in our project.
I saw related posts speaking of BCEL and Jar Analyzer updates, but I'm not
able to connect the dots as to how to take action. Harmless or not, how
can I get rid of them while still keeping the dependency report?
Thank you.
...
Visiting non-standard Signature object
Visiting non-standard Signature object
Visiting non-standard Signature object
Visiting non-standard Signature object
Visiting non-standard Signature object
Visiting non-standard Signature object
Visiting non-standard Signature object
Visiting non-standard Signature object
Visiting non-standard Signature object
Visiting non-standard Signature object
Visiting non-standard Signature object
Visiting non-standard Signature object
Visiting non-standard Signature object
Visiting non-standard Signature object
[INFO]
------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 6 minutes 46 seconds
[INFO] Finished at: Fri Apr 03 12:35:06 CDT 2009
[INFO] Final Memory: 63M/254M
[INFO]
------------------------------------------------------------------------
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: Help with patching a release?
Posted by Todd Thiessen <th...@nortel.com>.
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:brianf@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:dhicks@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-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: Help with patching a release?
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
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:dhicks@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-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