You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by MATHUS Baptiste <ma...@mipih.fr> on 2008/03/28 07:53:12 UTC
RE : [deploy-plugin] Abort deploy when a target is present
Great news!
I had a quick look on https://svn.apache.org/repos/asf/maven/plugins/trunk/maven-deploy-plugin/ and did not see any log related to it.
So was there already a logged bug about this: http://jira.codehaus.org/browse/MDEPLOY-74
What/where is the "new code", some 3.x or something? So, is there another svn repository for this? In fact, I'd be happy to be able to either use a new released version or help merging back this feature if possible.
Cheers
-------- Message d'origine--------
De: Brian E. Fox [mailto:brianf@reply.infinity.nu]
Date: jeu. 27/03/2008 18:45
�: Maven Users List
Objet : RE: [deploy-plugin] Abort deploy when a target is present
This is the default in the new code, but it wasn't merged back to 2.0.x
I believe.
-----Original Message-----
From: MATHUS Baptiste [mailto:mathus.b@mipih.fr]
Sent: Thursday, March 27, 2008 9:32 AM
To: Maven Users List
Subject: [deploy-plugin] Abort deploy when a target is present
Hi all,
Recently, some developers did a release manually. So they put a release
version in the pom and triggered a deploy. Everything fine but...
The thing is: they forgot to re-update the pom.version to a new snapshot
version.
So, as the code is continuously integrated, at each new commit, the
recent release was "automatically" overridden many times with the
snapshot code before realizing it :-/.
So, what I would like is to be able to put an additional option for
maven when run inside the continuous integration server, something like
-DdontOverrideRelease, that would make fail the deployment if the
released artefact is already present.
I've taken a quick look at
http://maven.apache.org/plugins/maven-deploy-plugin/deploy-mojo.html but
it seems it's not currently possible.
What do you think? Can a file an feature request about it in the plugin
tracker?
Thanks a lot.
Cheers.
--
Baptiste
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: RE : [deploy-plugin] Abort deploy when a target is present
Posted by solo1970 <so...@ericsson.com>.
Somehow I'm getting a little bit lost!!! I tried to read the feeds but I
don't quite get it!
I'm just starting out with Maven (ver. 2.0.9) and I would like to have this
feature of NO re-reployement of the same version. Can someone summarize?
How do I do this? Is it available????
Sonia
MATHUS Baptiste wrote:
>
> Hi all,
>
> If some people were still interested in this subject, I found the
> code&commit Brian was speaking about.
> I also commented the bug I logged:
> http://jira.codehaus.org/browse/MDEPLOY-74?focusedCommentId=129147#action_129147
>
> The related improvement request (logged by Jason):
> http://jira.codehaus.org/browse/MARTIFACT-6
>
> With this modification, at the moment, the situation will be reversed: you
> won't be able to redeploy an artifact that has already been deployed (no
> problem for snapshot, which is taken apart). So, don't do mistakes :).
> You'll have to connect to your repository and manually deploy the wrong
> artifact(s).
> Anyway, Imo, it's actually far better to have no option in this case than
> in the old one (being able to redeploy any time you want).
>
> Cheers.
>
> -----Original Message-----
> From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
> Sent: Fri 3/28/2008 2:59 PM
> To: Maven Users List
> Subject: RE: RE : [deploy-plugin] Abort deploy when a target is present
>
> I'd have to check on this. I know in 2.1 it's on by default and there is
> no way to force it. Perhaps Jason put it in the wagon manager or something
> and not the plugin.
>
> -----Original Message-----
> From: MATHUS Baptiste [mailto:mathus.b@mipih.fr]
> Sent: Friday, March 28, 2008 2:53 AM
> To: Maven Users List
> Subject: RE : [deploy-plugin] Abort deploy when a target is present
>
> Great news!
>
> I had a quick look on
> https://svn.apache.org/repos/asf/maven/plugins/trunk/maven-deploy-plugin/
> and did not see any log related to it.
> So was there already a logged bug about this:
> http://jira.codehaus.org/browse/MDEPLOY-74
>
> What/where is the "new code", some 3.x or something? So, is there another
> svn repository for this? In fact, I'd be happy to be able to either use a
> new released version or help merging back this feature if possible.
>
> Cheers
>
> -------- Message d'origine--------
> De: Brian E. Fox [mailto:brianf@reply.infinity.nu]
> Date: jeu. 27/03/2008 18:45
> À: Maven Users List
> Objet : RE: [deploy-plugin] Abort deploy when a target is present
>
> This is the default in the new code, but it wasn't merged back to 2.0.x I
> believe.
>
> -----Original Message-----
> From: MATHUS Baptiste [mailto:mathus.b@mipih.fr]
> Sent: Thursday, March 27, 2008 9:32 AM
> To: Maven Users List
> Subject: [deploy-plugin] Abort deploy when a target is present
>
> Hi all,
>
> Recently, some developers did a release manually. So they put a release
> version in the pom and triggered a deploy. Everything fine but...
> The thing is: they forgot to re-update the pom.version to a new snapshot
> version.
>
> So, as the code is continuously integrated, at each new commit, the recent
> release was "automatically" overridden many times with the snapshot code
> before realizing it :-/.
> So, what I would like is to be able to put an additional option for maven
> when run inside the continuous integration server, something like
> -DdontOverrideRelease, that would make fail the deployment if the released
> artefact is already present.
>
> I've taken a quick look at
> http://maven.apache.org/plugins/maven-deploy-plugin/deploy-mojo.html but
> it seems it's not currently possible.
> What do you think? Can a file an feature request about it in the plugin
> tracker?
>
> Thanks a lot.
>
> Cheers.
> --
> Baptiste
>
>
> ---------------------------------------------------------------------
> 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
>
--
View this message in context: http://www.nabble.com/-deploy-plugin--Abort-deploy-when-a-target-is-present-tp16329568p20800811.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE : [deploy-plugin] Abort deploy when a target is present
Posted by MATHUS Baptiste <ma...@mipih.fr>.
Hi all,
If some people were still interested in this subject, I found the code&commit Brian was speaking about.
I also commented the bug I logged:
http://jira.codehaus.org/browse/MDEPLOY-74?focusedCommentId=129147#action_129147
The related improvement request (logged by Jason): http://jira.codehaus.org/browse/MARTIFACT-6
With this modification, at the moment, the situation will be reversed: you won't be able to redeploy an artifact that has already been deployed (no problem for snapshot, which is taken apart). So, don't do mistakes :). You'll have to connect to your repository and manually deploy the wrong artifact(s).
Anyway, Imo, it's actually far better to have no option in this case than in the old one (being able to redeploy any time you want).
Cheers.
-----Original Message-----
From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
Sent: Fri 3/28/2008 2:59 PM
To: Maven Users List
Subject: RE: RE : [deploy-plugin] Abort deploy when a target is present
I'd have to check on this. I know in 2.1 it's on by default and there is no way to force it. Perhaps Jason put it in the wagon manager or something and not the plugin.
-----Original Message-----
From: MATHUS Baptiste [mailto:mathus.b@mipih.fr]
Sent: Friday, March 28, 2008 2:53 AM
To: Maven Users List
Subject: RE : [deploy-plugin] Abort deploy when a target is present
Great news!
I had a quick look on https://svn.apache.org/repos/asf/maven/plugins/trunk/maven-deploy-plugin/ and did not see any log related to it.
So was there already a logged bug about this: http://jira.codehaus.org/browse/MDEPLOY-74
What/where is the "new code", some 3.x or something? So, is there another svn repository for this? In fact, I'd be happy to be able to either use a new released version or help merging back this feature if possible.
Cheers
-------- Message d'origine--------
De: Brian E. Fox [mailto:brianf@reply.infinity.nu]
Date: jeu. 27/03/2008 18:45
�: Maven Users List
Objet : RE: [deploy-plugin] Abort deploy when a target is present
This is the default in the new code, but it wasn't merged back to 2.0.x I believe.
-----Original Message-----
From: MATHUS Baptiste [mailto:mathus.b@mipih.fr]
Sent: Thursday, March 27, 2008 9:32 AM
To: Maven Users List
Subject: [deploy-plugin] Abort deploy when a target is present
Hi all,
Recently, some developers did a release manually. So they put a release version in the pom and triggered a deploy. Everything fine but...
The thing is: they forgot to re-update the pom.version to a new snapshot version.
So, as the code is continuously integrated, at each new commit, the recent release was "automatically" overridden many times with the snapshot code before realizing it :-/.
So, what I would like is to be able to put an additional option for maven when run inside the continuous integration server, something like -DdontOverrideRelease, that would make fail the deployment if the released artefact is already present.
I've taken a quick look at
http://maven.apache.org/plugins/maven-deploy-plugin/deploy-mojo.html but it seems it's not currently possible.
What do you think? Can a file an feature request about it in the plugin tracker?
Thanks a lot.
Cheers.
--
Baptiste
---------------------------------------------------------------------
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: RE : [deploy-plugin] Abort deploy when a target is present
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
I'd have to check on this. I know in 2.1 it's on by default and there is no way to force it. Perhaps Jason put it in the wagon manager or something and not the plugin.
-----Original Message-----
From: MATHUS Baptiste [mailto:mathus.b@mipih.fr]
Sent: Friday, March 28, 2008 2:53 AM
To: Maven Users List
Subject: RE : [deploy-plugin] Abort deploy when a target is present
Great news!
I had a quick look on https://svn.apache.org/repos/asf/maven/plugins/trunk/maven-deploy-plugin/ and did not see any log related to it.
So was there already a logged bug about this: http://jira.codehaus.org/browse/MDEPLOY-74
What/where is the "new code", some 3.x or something? So, is there another svn repository for this? In fact, I'd be happy to be able to either use a new released version or help merging back this feature if possible.
Cheers
-------- Message d'origine--------
De: Brian E. Fox [mailto:brianf@reply.infinity.nu]
Date: jeu. 27/03/2008 18:45
À: Maven Users List
Objet : RE: [deploy-plugin] Abort deploy when a target is present
This is the default in the new code, but it wasn't merged back to 2.0.x I believe.
-----Original Message-----
From: MATHUS Baptiste [mailto:mathus.b@mipih.fr]
Sent: Thursday, March 27, 2008 9:32 AM
To: Maven Users List
Subject: [deploy-plugin] Abort deploy when a target is present
Hi all,
Recently, some developers did a release manually. So they put a release version in the pom and triggered a deploy. Everything fine but...
The thing is: they forgot to re-update the pom.version to a new snapshot version.
So, as the code is continuously integrated, at each new commit, the recent release was "automatically" overridden many times with the snapshot code before realizing it :-/.
So, what I would like is to be able to put an additional option for maven when run inside the continuous integration server, something like -DdontOverrideRelease, that would make fail the deployment if the released artefact is already present.
I've taken a quick look at
http://maven.apache.org/plugins/maven-deploy-plugin/deploy-mojo.html but it seems it's not currently possible.
What do you think? Can a file an feature request about it in the plugin tracker?
Thanks a lot.
Cheers.
--
Baptiste
---------------------------------------------------------------------
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