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/27 14:32:29 UTC
[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
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
RE : [deploy-plugin] Abort deploy when a target is present
Posted by MATHUS Baptiste <ma...@mipih.fr>.
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: [deploy-plugin] Abort deploy when a target is present
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
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: [deploy-plugin] Abort deploy when a target is present
Posted by Wayne Fay <wa...@gmail.com>.
Others have asked about this previously. I would imagine it is filed
in JIRA if you go look for it.
The general response is, you can manage the rwx bits on your deployed
artifacts to avoid this happening. Off the top of my head, I think a
cron job that modifies the ACLs for deployed non-snapshot artifacts
that runs once an hour should do it. Or perhaps you could modify the
umask for the user that runs the deploys. Or any number of
alternatives.
Also I would assume the various repo managers are building this
functionality into their products (eg, do not allow to overwrite,
return fail when attempted).
If you're just using a dumb file repo, you're going to have to be
responsible for this on your own for now, at least until someone gets
inspired to add bits to wagon and other places to support the feature.
Wayne
On 3/27/08, Jeff MAURY <je...@jeffmaury.com> wrote:
> I think it should be defined at the repository definition level.
>
> Jeff MAURY
>
> On Thu, Mar 27, 2008 at 2:32 PM, MATHUS Baptiste <ma...@mipih.fr> wrote:
>
> > 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
> >
> >
>
>
> --
> La mélancolie c'est communiste
> Tout le monde y a droit de temps en temps
> La mélancolie n'est pas capitaliste
> C'est même gratuit pour les perdants
> La mélancolie c'est pacifiste
> On ne lui rentre jamais dedans
> La mélancolie oh tu sais ça existe
> Elle se prend même avec des gants
> La mélancolie c'est pour les syndicalistes
> Il faut juste sa carte de permanent
>
> Miossec (2006)
>
> http://www.jeffmaury.com
> http://riadiscuss.jeffmaury.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>.
Don't worry. I'm totally aware of how the open source community works and wholeheartely support it :).
I'll never complain if something isn't done quickly. If I really need something, I'll just try and provide the patch myself.
In the meantime, I'll log the improvement request (http://jira.codehaus.org/browse/MDEPLOY-74).
Later, I might provide a patch in addition.
Moreover, in the current case, I guess this is something I could do as a maven plugin development big beginner :).
Cheers.
> -----Message d'origine-----
> De : Wayne Fay [mailto:waynefay@gmail.com]
> Envoyé : jeudi 27 mars 2008 16:48
> À : Maven Users List
> Objet : Re: [deploy-plugin] Abort deploy when a target is present
>
> As soon as you write the code and contribute it, I'm sure it
> will be greeted with open arms. ;-)
>
> Until someone gets really inspired to do this, I just have no
> real expectation for when it will happen. Many people are
> solving this problem with other solutions (previously
> mentioned) so its considered a New Feature or Improvement,
> rather than a real bug, so the priority is low.
>
> So, that's why I suggest finding another way to solve this issue.
>
> Wayne
>
> On 3/27/08, MATHUS Baptiste <ma...@mipih.fr> wrote:
> > Well:
> > * I think you're right: I'll open a thread in the archiva
> users ML to see if it's possible. At least it would be a good
> idea for improvement.
> > * But I also think maven-deploy-plugin would be better if
> it had this option. At least it would help debugging. Or some
> option like -DdryRun=true to just simulate the distant
> artifact, and displaying if one was overridden or not.
> >
> > Cheers.
> >
> > > -----Message d'origine-----
> > > De : jeffmaury@gmail.com [mailto:jeffmaury@gmail.com] De
> la part de
> > > Jeff MAURY Envoyé : jeudi 27 mars 2008 15:16 À : Maven Users List
> > > Objet : Re: [deploy-plugin] Abort deploy when a target is present
> > >
> > > I think it should be defined at the repository definition level.
> > >
> > > Jeff MAURY
> > >
> > > On Thu, Mar 27, 2008 at 2:32 PM, MATHUS Baptiste
> <ma...@mipih.fr>
> > > wrote:
> > >
> > > > 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
> > > >
> > > >
> > >
> > >
> > > --
> > > La mélancolie c'est communiste
> > > Tout le monde y a droit de temps en temps La mélancolie n'est pas
> > > capitaliste C'est même gratuit pour les perdants La
> mélancolie c'est
> > > pacifiste On ne lui rentre jamais dedans La mélancolie oh
> tu sais ça
> > > existe Elle se prend même avec des gants La mélancolie c'est pour
> > > les syndicalistes Il faut juste sa carte de permanent
> > >
> > > Miossec (2006)
> > >
> > > http://www.jeffmaury.com
> > > http://riadiscuss.jeffmaury.com
> > >
> >
> >
> ---------------------------------------------------------------------
> > 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: [deploy-plugin] Abort deploy when a target is present
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
The code needs to be moved to the deploy plugin and then the wagons in
2.0 and 2.1 updated to use it correctly. 2.1 will be a while before it's
ready for production use.
-----Original Message-----
From: Ben Lidgey [mailto:ben.lidgey@inuknetworks.com]
Sent: Wednesday, April 02, 2008 9:31 AM
To: Maven Users List
Subject: RE: [deploy-plugin] Abort deploy when a target is present
> -----Original Message-----
> From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
> Sent: 27 March 2008 17:52
> To: Maven Users List
> Subject: RE: [deploy-plugin] Abort deploy when a target is present
>
> It's done... there is a force flag to force a deploy if you
> need to, otherwise it will fail.
Is this only in the 2.1 code base? It would be really helpful in our CI
builds. Is there a chance it would be ported to 2.0.x or if not, can
some kind soul point me in the direction of the roadmap for 2.1 and the
expected release dates?
Ben
This e-mail is confidential and intended solely for the use of the
individual(s) to whom it is addressed. Any views or opinions expressed
are those of the author. If you are not the intended recipient, please
be advised that any use, dissemination, printing or copying of this
email is strictly prohibited.
---------------------------------------------------------------------
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: [deploy-plugin] Abort deploy when a target is present
Posted by Wayne Fay <wa...@gmail.com>.
Wow, I obviously have not been keeping up with this issue. We have
various internal controls such that I don't particularly care about it
right now.
Thanks Brian.
Wayne
On 3/27/08, Brian E. Fox <br...@reply.infinity.nu> wrote:
> It's done... there is a force flag to force a deploy if you need to, otherwise it will fail.
>
> -----Original Message-----
> From: Wayne Fay [mailto:waynefay@gmail.com]
> Sent: Thursday, March 27, 2008 11:48 AM
> To: Maven Users List
> Subject: Re: [deploy-plugin] Abort deploy when a target is present
>
> As soon as you write the code and contribute it, I'm sure it will be
> greeted with open arms. ;-)
>
> Until someone gets really inspired to do this, I just have no real
> expectation for when it will happen. Many people are solving this
> problem with other solutions (previously mentioned) so its considered
> a New Feature or Improvement, rather than a real bug, so the priority
> is low.
>
> So, that's why I suggest finding another way to solve this issue.
>
> Wayne
>
> On 3/27/08, MATHUS Baptiste <ma...@mipih.fr> wrote:
> > Well:
> > * I think you're right: I'll open a thread in the archiva users ML to see if it's possible. At least it would be a good idea for improvement.
> > * But I also think maven-deploy-plugin would be better if it had this option. At least it would help debugging. Or some option like -DdryRun=true to just simulate the distant artifact, and displaying if one was overridden or not.
> >
> > Cheers.
> >
> > > -----Message d'origine-----
> > > De : jeffmaury@gmail.com [mailto:jeffmaury@gmail.com] De la
> > > part de Jeff MAURY
> > > Envoyé : jeudi 27 mars 2008 15:16
> > > À : Maven Users List
> > > Objet : Re: [deploy-plugin] Abort deploy when a target is present
> > >
> > > I think it should be defined at the repository definition level.
> > >
> > > Jeff MAURY
> > >
> > > On Thu, Mar 27, 2008 at 2:32 PM, MATHUS Baptiste
> > > <ma...@mipih.fr> wrote:
> > >
> > > > 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
> > > >
> > > >
> > >
> > >
> > > --
> > > La mélancolie c'est communiste
> > > Tout le monde y a droit de temps en temps La mélancolie n'est
> > > pas capitaliste C'est même gratuit pour les perdants La
> > > mélancolie c'est pacifiste On ne lui rentre jamais dedans La
> > > mélancolie oh tu sais ça existe Elle se prend même avec des
> > > gants La mélancolie c'est pour les syndicalistes Il faut
> > > juste sa carte de permanent
> > >
> > > Miossec (2006)
> > >
> > > http://www.jeffmaury.com
> > > http://riadiscuss.jeffmaury.com
> > >
> >
> > ---------------------------------------------------------------------
> > 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: [deploy-plugin] Abort deploy when a target is present
Posted by Ben Lidgey <be...@inuknetworks.com>.
> -----Original Message-----
> From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
> Sent: 27 March 2008 17:52
> To: Maven Users List
> Subject: RE: [deploy-plugin] Abort deploy when a target is present
>
> It's done... there is a force flag to force a deploy if you
> need to, otherwise it will fail.
Is this only in the 2.1 code base? It would be really helpful in our CI builds. Is there a chance it would be ported to 2.0.x or if not, can some kind soul point me in the direction of the roadmap for 2.1 and the expected release dates?
Ben
This e-mail is confidential and intended solely for the use of the individual(s) to whom it is addressed. Any views or opinions expressed are those of the author. If you are not the intended recipient, please be advised that any use, dissemination, printing or copying of this email is strictly prohibited.
---------------------------------------------------------------------
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 "Brian E. Fox" <br...@reply.infinity.nu>.
It's done... there is a force flag to force a deploy if you need to, otherwise it will fail.
-----Original Message-----
From: Wayne Fay [mailto:waynefay@gmail.com]
Sent: Thursday, March 27, 2008 11:48 AM
To: Maven Users List
Subject: Re: [deploy-plugin] Abort deploy when a target is present
As soon as you write the code and contribute it, I'm sure it will be
greeted with open arms. ;-)
Until someone gets really inspired to do this, I just have no real
expectation for when it will happen. Many people are solving this
problem with other solutions (previously mentioned) so its considered
a New Feature or Improvement, rather than a real bug, so the priority
is low.
So, that's why I suggest finding another way to solve this issue.
Wayne
On 3/27/08, MATHUS Baptiste <ma...@mipih.fr> wrote:
> Well:
> * I think you're right: I'll open a thread in the archiva users ML to see if it's possible. At least it would be a good idea for improvement.
> * But I also think maven-deploy-plugin would be better if it had this option. At least it would help debugging. Or some option like -DdryRun=true to just simulate the distant artifact, and displaying if one was overridden or not.
>
> Cheers.
>
> > -----Message d'origine-----
> > De : jeffmaury@gmail.com [mailto:jeffmaury@gmail.com] De la
> > part de Jeff MAURY
> > Envoyé : jeudi 27 mars 2008 15:16
> > À : Maven Users List
> > Objet : Re: [deploy-plugin] Abort deploy when a target is present
> >
> > I think it should be defined at the repository definition level.
> >
> > Jeff MAURY
> >
> > On Thu, Mar 27, 2008 at 2:32 PM, MATHUS Baptiste
> > <ma...@mipih.fr> wrote:
> >
> > > 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
> > >
> > >
> >
> >
> > --
> > La mélancolie c'est communiste
> > Tout le monde y a droit de temps en temps La mélancolie n'est
> > pas capitaliste C'est même gratuit pour les perdants La
> > mélancolie c'est pacifiste On ne lui rentre jamais dedans La
> > mélancolie oh tu sais ça existe Elle se prend même avec des
> > gants La mélancolie c'est pour les syndicalistes Il faut
> > juste sa carte de permanent
> >
> > Miossec (2006)
> >
> > http://www.jeffmaury.com
> > http://riadiscuss.jeffmaury.com
> >
>
> ---------------------------------------------------------------------
> 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: [deploy-plugin] Abort deploy when a target is present
Posted by Wayne Fay <wa...@gmail.com>.
As soon as you write the code and contribute it, I'm sure it will be
greeted with open arms. ;-)
Until someone gets really inspired to do this, I just have no real
expectation for when it will happen. Many people are solving this
problem with other solutions (previously mentioned) so its considered
a New Feature or Improvement, rather than a real bug, so the priority
is low.
So, that's why I suggest finding another way to solve this issue.
Wayne
On 3/27/08, MATHUS Baptiste <ma...@mipih.fr> wrote:
> Well:
> * I think you're right: I'll open a thread in the archiva users ML to see if it's possible. At least it would be a good idea for improvement.
> * But I also think maven-deploy-plugin would be better if it had this option. At least it would help debugging. Or some option like -DdryRun=true to just simulate the distant artifact, and displaying if one was overridden or not.
>
> Cheers.
>
> > -----Message d'origine-----
> > De : jeffmaury@gmail.com [mailto:jeffmaury@gmail.com] De la
> > part de Jeff MAURY
> > Envoyé : jeudi 27 mars 2008 15:16
> > À : Maven Users List
> > Objet : Re: [deploy-plugin] Abort deploy when a target is present
> >
> > I think it should be defined at the repository definition level.
> >
> > Jeff MAURY
> >
> > On Thu, Mar 27, 2008 at 2:32 PM, MATHUS Baptiste
> > <ma...@mipih.fr> wrote:
> >
> > > 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
> > >
> > >
> >
> >
> > --
> > La mélancolie c'est communiste
> > Tout le monde y a droit de temps en temps La mélancolie n'est
> > pas capitaliste C'est même gratuit pour les perdants La
> > mélancolie c'est pacifiste On ne lui rentre jamais dedans La
> > mélancolie oh tu sais ça existe Elle se prend même avec des
> > gants La mélancolie c'est pour les syndicalistes Il faut
> > juste sa carte de permanent
> >
> > Miossec (2006)
> >
> > http://www.jeffmaury.com
> > http://riadiscuss.jeffmaury.com
> >
>
> ---------------------------------------------------------------------
> 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: [deploy-plugin] Abort deploy when a target is present
Posted by MATHUS Baptiste <ma...@mipih.fr>.
Well:
* I think you're right: I'll open a thread in the archiva users ML to see if it's possible. At least it would be a good idea for improvement.
* But I also think maven-deploy-plugin would be better if it had this option. At least it would help debugging. Or some option like -DdryRun=true to just simulate the distant artifact, and displaying if one was overridden or not.
Cheers.
> -----Message d'origine-----
> De : jeffmaury@gmail.com [mailto:jeffmaury@gmail.com] De la
> part de Jeff MAURY
> Envoyé : jeudi 27 mars 2008 15:16
> À : Maven Users List
> Objet : Re: [deploy-plugin] Abort deploy when a target is present
>
> I think it should be defined at the repository definition level.
>
> Jeff MAURY
>
> On Thu, Mar 27, 2008 at 2:32 PM, MATHUS Baptiste
> <ma...@mipih.fr> wrote:
>
> > 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
> >
> >
>
>
> --
> La mélancolie c'est communiste
> Tout le monde y a droit de temps en temps La mélancolie n'est
> pas capitaliste C'est même gratuit pour les perdants La
> mélancolie c'est pacifiste On ne lui rentre jamais dedans La
> mélancolie oh tu sais ça existe Elle se prend même avec des
> gants La mélancolie c'est pour les syndicalistes Il faut
> juste sa carte de permanent
>
> Miossec (2006)
>
> http://www.jeffmaury.com
> http://riadiscuss.jeffmaury.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 Jeff MAURY <je...@jeffmaury.com>.
I think it should be defined at the repository definition level.
Jeff MAURY
On Thu, Mar 27, 2008 at 2:32 PM, MATHUS Baptiste <ma...@mipih.fr> wrote:
> 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
>
>
--
La mélancolie c'est communiste
Tout le monde y a droit de temps en temps
La mélancolie n'est pas capitaliste
C'est même gratuit pour les perdants
La mélancolie c'est pacifiste
On ne lui rentre jamais dedans
La mélancolie oh tu sais ça existe
Elle se prend même avec des gants
La mélancolie c'est pour les syndicalistes
Il faut juste sa carte de permanent
Miossec (2006)
http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com
RE: [deploy-plugin] Abort deploy when a target is present
Posted by solo1970 <so...@ericsson.com>.
Our repository Manager is Archiva and it can't do it....
Sonia
Nord, James-2 wrote:
>
> You need a repository manager.
> Nexus can do this - others may to.
>
> http://nexus.sonatype.org/about/faq.html#QHowdoIdisableartifactredeploym
> ent
>
> /James
>
>> -----Original Message-----
>> From: solo1970 [mailto:sonia.lodovichetti@ericsson.com]
>> Sent: 03 December 2008 15:02
>> To: users@maven.apache.org
>> Subject: Re: [deploy-plugin] Abort deploy when a target is present
>>
>>
>> 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,
>> >
>> > 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
>> >
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/-deploy-plugin--Abort-deploy-when-a-targ
>> et-is-present-tp16329568p20814596.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
>>
>>
>
> *********************************************************************************************************
> This e-mail is confidential, the property of NDS Ltd and intended for the
> addressee only. Any dissemination, copying or distribution of this
> message or any attachments by anyone other than the intended recipient is
> strictly prohibited. If you have received this message in error, please
> immediately notify the postmaster@nds.com and destroy the original
> message. Messages sent to and from NDS may be monitored. NDS cannot
> guarantee any message delivery method is secure or error-free.
> Information could be intercepted, corrupted, lost, destroyed, arrive late
> or incomplete, or contain viruses. We do not accept responsibility for
> any errors or omissions in this message and/or attachment that arise as a
> result of transmission. You should carry out your own virus checks before
> opening any attachment. Any views or opinions presented are solely those
> of the author and do not necessarily represent those of NDS.
>
> To protect the environment please do not print this e-mail unless
> necessary.
>
> NDS Limited Registered office: One Heathrow Boulevard, 286 Bath Road, West
> Drayton, Middlesex, UB7 0DQ, United Kingdom. A company registered in
> England and Wales Registered no. 3080780 VAT no. GB 603 8808 40-00
> **********************************************************************************************************
>
>
> ---------------------------------------------------------------------
> 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-tp16329568p20815707.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 "Nord, James" <JN...@nds.com>.
You need a repository manager.
Nexus can do this - others may to.
http://nexus.sonatype.org/about/faq.html#QHowdoIdisableartifactredeploym
ent
/James
> -----Original Message-----
> From: solo1970 [mailto:sonia.lodovichetti@ericsson.com]
> Sent: 03 December 2008 15:02
> To: users@maven.apache.org
> Subject: Re: [deploy-plugin] Abort deploy when a target is present
>
>
> 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,
> >
> > 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
> >
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/-deploy-plugin--Abort-deploy-when-a-targ
> et-is-present-tp16329568p20814596.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
>
>
*********************************************************************************************************
This e-mail is confidential, the property of NDS Ltd and intended for the addressee only. Any dissemination, copying or distribution of this message or any attachments by anyone other than the intended recipient is strictly prohibited. If you have received this message in error, please immediately notify the postmaster@nds.com and destroy the original message. Messages sent to and from NDS may be monitored. NDS cannot guarantee any message delivery method is secure or error-free. Information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. We do not accept responsibility for any errors or omissions in this message and/or attachment that arise as a result of transmission. You should carry out your own virus checks before opening any attachment. Any views or opinions presented are solely those of the author and do not necessarily represent those of NDS.
To protect the environment please do not print this e-mail unless necessary.
NDS Limited Registered office: One Heathrow Boulevard, 286 Bath Road, West Drayton, Middlesex, UB7 0DQ, United Kingdom. A company registered in England and Wales Registered no. 3080780 VAT no. GB 603 8808 40-00
**********************************************************************************************************
---------------------------------------------------------------------
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 Todd Thiessen <th...@nortel.com>.
Well, I am pretty new as well but I have been putting some thought into
this.
If you are deploying snapshots, simply the "unique version" option. This
ensures your snapshots never get clobbered.
For releases, I would use the release plugin. This plugin calculates for
you, or asks you for, a new version to use after the release. It
modifies the <version> tag of your pom with the new version and commits
it back to source control so you can't "clobber" an existing release
when you wish to generate a new one.
---
Todd Thiessen
-----Original Message-----
From: solo1970 [mailto:sonia.lodovichetti@ericsson.com]
Sent: Wednesday, December 03, 2008 10:02 AM
To: users@maven.apache.org
Subject: Re: [deploy-plugin] Abort deploy when a target is present
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,
>
> 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
>
>
>
--
View this message in context:
http://www.nabble.com/-deploy-plugin--Abort-deploy-when-a-target-is-pres
ent-tp16329568p20814596.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
---------------------------------------------------------------------
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 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,
>
> 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
>
>
>
--
View this message in context: http://www.nabble.com/-deploy-plugin--Abort-deploy-when-a-target-is-present-tp16329568p20814596.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