You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Jim McCaskey <ji...@pervasive.com> on 2009/03/26 03:17:26 UTC
How to perform a deploy only
Hello all,
I have several components all built from a top level pom. This works great for accelerating users to be able to build a lot of stuff quickly but is giving me some fits when trying to deploy. Up to this point I have been using deploy:deploy-file to get built components into our local repository after a full build is successful, but this is labor intensive.
I would like to be able to run some variation of "mvn deploy" from the top level. I have figured out how to skip things using the FAQ here:
http://maven.apache.org/plugins/maven-deploy-plugin/faq.html#skip
But I do NOT want it to do anything other than deploy. I have googled for this but have not turned up anything useful. I was surprised that the documentation does not suggest how to do this. This is the correct deploy documentation I think.
http://maven.apache.org/plugins/maven-deploy-plugin/
Anyway, any help would be appreciated.
Thanks!
-Jim
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: How to perform a deploy only
Posted by B Smith-Mannschott <bs...@gmail.com>.
On Thu, Mar 26, 2009 at 03:17, Jim McCaskey <ji...@pervasive.com> wrote:
> Hello all,
>
> I have several components all built from a top level pom. This works great for accelerating users to be able to build a lot of stuff quickly but is giving me some fits when trying to deploy. Up to this point I have been using deploy:deploy-file to get built components into our local repository after a full build is successful, but this is labor intensive.
My Guess: It sounds like you're describing a multi-module build where
the "top-level" pom naming the modules to be built is also parent to
the sub-modules. You want to deploy just the top-level pom, so others
can build against it. Correct? You don't want to deploy all the
sub-modules each time you do this because they may not be in a stable
state.
(1) Have you considered "mvn --non-recursive deploy"?
(2) You do realize that the pom that defines the modules does not have
to be the same as the common parent pom, yes?
<http://www.sonatype.com/books/maven-book/reference/pom-relationships-sect-multi-vs-inherit.html#fig-maven-book>
// ben
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: SpeedUp the release process
Posted by Kalle Korhonen <ka...@gmail.com>.
Hudson deploys our site nightly, we don't publish the site at all with
releases - the release now takes only a fraction of what it used to take
with site deploy (15-20mins compared to 2.5h).
Kalle
On Fri, Mar 27, 2009 at 2:57 PM, Stephen Connolly <
stephen.alan.connolly@gmail.com> wrote:
> we deploy the site to a local directory and then afterwards copy the site
> to
> the web server location
>
> 2009/3/27 Hoehmann, Andreas <an...@siemens.com>
>
> > Hi folks,
> >
> > i have a multi-module-project (~30 artifacts).
> >
> > I wrote a little script to release the whole project from root
> >
> > - check dependencies
> > - try site-build
> > - try release:prepare
> > - clean up
> > - release:prepare
> > - release:perform
> > - deploy new snapshots
> >
> > My repository works with webdav behind a apache2. The release of the 30
> > artifacts is running ~ 2 hours ... and the most time cost the deployment
> of
> > the project-sites (upload javadoc etc.) ... is there a better way to
> deploy
> > a project-site, e.g. deploy in a local mounten networkdevice, or in a
> local
> > directory and the syn to the server ?
> >
> > Ideas are welcome :)
> >
> > Regards
> > andreas
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
AW: SpeedUp the release process
Posted by "Hoehmann, Andreas" <an...@siemens.com>.
how can i define the local directory?
please could you post a pom.xml snippet for that?
> -----Ursprüngliche Nachricht-----
> Von: Stephen Connolly [mailto:stephen.alan.connolly@gmail.com]
> Gesendet: Freitag, 27. März 2009 22:57
> An: Maven Users List
> Betreff: Re: SpeedUp the release process
>
> we deploy the site to a local directory and then afterwards
> copy the site to
> the web server location
>
> 2009/3/27 Hoehmann, Andreas <an...@siemens.com>
>
> > Hi folks,
> >
> > i have a multi-module-project (~30 artifacts).
> >
> > I wrote a little script to release the whole project from root
> >
> > - check dependencies
> > - try site-build
> > - try release:prepare
> > - clean up
> > - release:prepare
> > - release:perform
> > - deploy new snapshots
> >
> > My repository works with webdav behind a apache2. The
> release of the 30
> > artifacts is running ~ 2 hours ... and the most time cost
> the deployment of
> > the project-sites (upload javadoc etc.) ... is there a
> better way to deploy
> > a project-site, e.g. deploy in a local mounten
> networkdevice, or in a local
> > directory and the syn to the server ?
> >
> > Ideas are welcome :)
> >
> > Regards
> > andreas
> >
> ---------------------------------------------------------------------
> > 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: SpeedUp the release process
Posted by Stephen Connolly <st...@gmail.com>.
we deploy the site to a local directory and then afterwards copy the site to
the web server location
2009/3/27 Hoehmann, Andreas <an...@siemens.com>
> Hi folks,
>
> i have a multi-module-project (~30 artifacts).
>
> I wrote a little script to release the whole project from root
>
> - check dependencies
> - try site-build
> - try release:prepare
> - clean up
> - release:prepare
> - release:perform
> - deploy new snapshots
>
> My repository works with webdav behind a apache2. The release of the 30
> artifacts is running ~ 2 hours ... and the most time cost the deployment of
> the project-sites (upload javadoc etc.) ... is there a better way to deploy
> a project-site, e.g. deploy in a local mounten networkdevice, or in a local
> directory and the syn to the server ?
>
> Ideas are welcome :)
>
> Regards
> andreas
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
RE: SpeedUp the release process
Posted by Martin Gainty <mg...@hotmail.com>.
you could save alot of time try to pull all your static artifacts to localRepository
but this may invite contention as BuildManager is downloading while you may be synch'ing
to shared structures..the solution of a simple lockfile as whomever has the lockfile
would have update access..all others would have read access to repository
http://docs.codehaus.org/display/MAVEN/Local+repository+separation
mit freundlichen grüßen
Martin
______________________________________________
Verzicht und Vertraulichkeitanmerkung / Disclaimer and confidentiality note
Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen.
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.
> From: andreas.hoehmann.ext@siemens.com
> To: users@maven.apache.org
> Date: Fri, 27 Mar 2009 19:25:11 +0100
> Subject: SpeedUp the release process
>
> Hi folks,
>
> i have a multi-module-project (~30 artifacts).
>
> I wrote a little script to release the whole project from root
>
> - check dependencies
> - try site-build
> - try release:prepare
> - clean up
> - release:prepare
> - release:perform
> - deploy new snapshots
>
> My repository works with webdav behind a apache2. The release of the 30 artifacts is running ~ 2 hours ... and the most time cost the deployment of the project-sites (upload javadoc etc.) ... is there a better way to deploy a project-site, e.g. deploy in a local mounten networkdevice, or in a local directory and the syn to the server ?
>
> Ideas are welcome :)
>
> Regards
> andreas
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
_________________________________________________________________
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
SpeedUp the release process
Posted by "Hoehmann, Andreas" <an...@siemens.com>.
Hi folks,
i have a multi-module-project (~30 artifacts).
I wrote a little script to release the whole project from root
- check dependencies
- try site-build
- try release:prepare
- clean up
- release:prepare
- release:perform
- deploy new snapshots
My repository works with webdav behind a apache2. The release of the 30 artifacts is running ~ 2 hours ... and the most time cost the deployment of the project-sites (upload javadoc etc.) ... is there a better way to deploy a project-site, e.g. deploy in a local mounten networkdevice, or in a local directory and the syn to the server ?
Ideas are welcome :)
Regards
andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: How to perform a deploy only
Posted by Todd Thiessen <th...@nortel.com>.
Brian.
I think what Jim is asking for is very reasonable. You just did a full
install of your multi-module project to ensure they all pass and work as
you expect to avoid encoutering those errors when doing a deploy and
only having 1/2 your projects up on your nexus repo. This isn't as
important for cutting new releases, since there is the release plugin,
but for deploying snapshots it would be nice to ensure all projects pass
all tests before deploying any of them. So running a mvn install, then a
mvn deployOnly work flow I think is very reasonable.
---
Todd Thiessen
> -----Original Message-----
> From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
> Sent: Wednesday, March 25, 2009 10:20 PM
> To: Maven Users List
> Subject: RE: How to perform a deploy only
>
> This really isn't a supported use case. Deploy is a phase and
> by definition all earlier phases run before the one you've
> asked for. Why would you not want to build before you deploy?
>
> -----Original Message-----
> From: Jim McCaskey [mailto:jim.mccaskey@pervasive.com]
> Sent: Wednesday, March 25, 2009 10:17 PM
> To: 'users@maven.apache.org'
> Subject: How to perform a deploy only
>
> Hello all,
>
> I have several components all built from a top level pom.
> This works great for accelerating users to be able to build a
> lot of stuff quickly but is giving me some fits when trying
> to deploy. Up to this point I have been using
> deploy:deploy-file to get built components into our local
> repository after a full build is successful, but this is
> labor intensive.
>
> I would like to be able to run some variation of "mvn deploy"
> from the top level. I have figured out how to skip things
> using the FAQ here:
>
> http://maven.apache.org/plugins/maven-deploy-plugin/faq.html#skip
>
> But I do NOT want it to do anything other than deploy. I
> have googled for this but have not turned up anything useful.
> I was surprised that the documentation does not suggest how
> to do this. This is the correct deploy documentation I think.
>
> http://maven.apache.org/plugins/maven-deploy-plugin/
>
> Anyway, any help would be appreciated.
>
> Thanks!
>
> -Jim
>
>
> ---------------------------------------------------------------------
> 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: How to perform a deploy only
Posted by Jim McCaskey <ji...@pervasive.com>.
Stephen,
Ah, this sounds like a very promising work around. I was unaware of the maven-stage-plugin. Short of a method to do it with deploy directly this may work.
Thanks for the suggestion!
-Jim
-----Original Message-----
From: Stephen Connolly [mailto:stephen.alan.connolly@gmail.com]
Sent: Thursday, March 26, 2009 1:13 AM
To: Maven Users List
Subject: Re: How to perform a deploy only
Well you could stage them yourself....
You need a staging repository... I see no reason why this cannot be file
based
You then need to do some scripting and use the maven-stage-plugin (
http://maven.apache.org/plugins/maven-stage-plugin/index.html) to copy the
contents of the staging repository to the real repository.
I normally have the distribution repository defined by a property in
settings.xml... so that you can just run
mvn deploy -Ddistribution.url=file:///staging-repo
and then run an ant script that does the mvn stage:copy for you
-Stephen
2009/3/26 Jim McCaskey <ji...@pervasive.com>
> Thanks for the suggestion. I have been trying to avoid using repository
> managers for a number of reasons that are beyond the scope of this thread.
> I may have to break down eventually...
>
> I'm surprised no one has needed this sort of feature, or maybe they have
> and that's why Nexus has the features that it does. I was hoping to find a
> Maven native (whatever native means in a highly pluggable architecture) way
> to do this that would not take much additional work.
>
> mvn -DdoNothingButDeploy=true deploy
>
> That would be about perfect. :)
>
> Would this even be consider for an enhancement request if I opened it?
> Perhaps I am the only one interested in such a thing.
>
> Thanks!
>
> -Jim
>
> -----Original Message-----
> From: Edelson, Justin [mailto:Justin.Edelson@mtvstaff.com]
> Sent: Wednesday, March 25, 2009 9:55 PM
> To: Maven Users List
> Subject: RE: How to perform a deploy only
>
> Brian can pitch his own stuff far better than I can, but this kind of
> transactional deployment can be done with Nexus' Staging feature.
>
> I realized after I sent my deploy:deploy suggestion that it probably
> wouldn't work without running at least the package phase, sorry to give you
> bad info. I'm reasonably confident with some light hacking you could write a
> plugin that essentially faked the build, but if the below is your use case
> and you can afford Nexus Pro, it's probably a better solution.
>
> Justin
>
>
> ________________________________
>
> From: Jim McCaskey [mailto:jim.mccaskey@pervasive.com]
> Sent: Wed 3/25/2009 10:37 PM
> To: 'Maven Users List'
> Subject: RE: How to perform a deploy only
>
>
>
> I have a whole bunch of components that are mostly interrelated but
> consumable individually by downstream builds. If I run deploy it basically
> starts deploying as it goes, so if a downstream component breaks for some
> reason then I am left with half of the components updated in the maven repo
> and half not. That's not really what we want.
>
> So ideally, we would run a build/test, make sure it all gets through
> completely, then deploy the resulting artifacts.
>
> -Jim
>
> -----Original Message-----
> From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
> Sent: Wednesday, March 25, 2009 9:20 PM
> To: Maven Users List
> Subject: RE: How to perform a deploy only
>
> This really isn't a supported use case. Deploy is a phase and by
> definition all earlier phases run before the one you've asked for. Why
> would you not want to build before you deploy?
>
> -----Original Message-----
> From: Jim McCaskey [mailto:jim.mccaskey@pervasive.com]
> Sent: Wednesday, March 25, 2009 10:17 PM
> To: 'users@maven.apache.org'
> Subject: How to perform a deploy only
>
> Hello all,
>
> I have several components all built from a top level pom. This works
> great for accelerating users to be able to build a lot of stuff quickly
> but is giving me some fits when trying to deploy. Up to this point I
> have been using deploy:deploy-file to get built components into our
> local repository after a full build is successful, but this is labor
> intensive.
>
> I would like to be able to run some variation of "mvn deploy" from the
> top level. I have figured out how to skip things using the FAQ here:
>
> http://maven.apache.org/plugins/maven-deploy-plugin/faq.html#skip
>
> But I do NOT want it to do anything other than deploy. I have googled
> for this but have not turned up anything useful. I was surprised that
> the documentation does not suggest how to do this. This is the correct
> deploy documentation I think.
>
> http://maven.apache.org/plugins/maven-deploy-plugin/
>
> Anyway, any help would be appreciated.
>
> Thanks!
>
> -Jim
>
>
> ---------------------------------------------------------------------
> 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: How to perform a deploy only
Posted by Stephen Connolly <st...@gmail.com>.
Well you could stage them yourself....
You need a staging repository... I see no reason why this cannot be file
based
You then need to do some scripting and use the maven-stage-plugin (
http://maven.apache.org/plugins/maven-stage-plugin/index.html) to copy the
contents of the staging repository to the real repository.
I normally have the distribution repository defined by a property in
settings.xml... so that you can just run
mvn deploy -Ddistribution.url=file:///staging-repo
and then run an ant script that does the mvn stage:copy for you
-Stephen
2009/3/26 Jim McCaskey <ji...@pervasive.com>
> Thanks for the suggestion. I have been trying to avoid using repository
> managers for a number of reasons that are beyond the scope of this thread.
> I may have to break down eventually...
>
> I'm surprised no one has needed this sort of feature, or maybe they have
> and that's why Nexus has the features that it does. I was hoping to find a
> Maven native (whatever native means in a highly pluggable architecture) way
> to do this that would not take much additional work.
>
> mvn -DdoNothingButDeploy=true deploy
>
> That would be about perfect. :)
>
> Would this even be consider for an enhancement request if I opened it?
> Perhaps I am the only one interested in such a thing.
>
> Thanks!
>
> -Jim
>
> -----Original Message-----
> From: Edelson, Justin [mailto:Justin.Edelson@mtvstaff.com]
> Sent: Wednesday, March 25, 2009 9:55 PM
> To: Maven Users List
> Subject: RE: How to perform a deploy only
>
> Brian can pitch his own stuff far better than I can, but this kind of
> transactional deployment can be done with Nexus' Staging feature.
>
> I realized after I sent my deploy:deploy suggestion that it probably
> wouldn't work without running at least the package phase, sorry to give you
> bad info. I'm reasonably confident with some light hacking you could write a
> plugin that essentially faked the build, but if the below is your use case
> and you can afford Nexus Pro, it's probably a better solution.
>
> Justin
>
>
> ________________________________
>
> From: Jim McCaskey [mailto:jim.mccaskey@pervasive.com]
> Sent: Wed 3/25/2009 10:37 PM
> To: 'Maven Users List'
> Subject: RE: How to perform a deploy only
>
>
>
> I have a whole bunch of components that are mostly interrelated but
> consumable individually by downstream builds. If I run deploy it basically
> starts deploying as it goes, so if a downstream component breaks for some
> reason then I am left with half of the components updated in the maven repo
> and half not. That's not really what we want.
>
> So ideally, we would run a build/test, make sure it all gets through
> completely, then deploy the resulting artifacts.
>
> -Jim
>
> -----Original Message-----
> From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
> Sent: Wednesday, March 25, 2009 9:20 PM
> To: Maven Users List
> Subject: RE: How to perform a deploy only
>
> This really isn't a supported use case. Deploy is a phase and by
> definition all earlier phases run before the one you've asked for. Why
> would you not want to build before you deploy?
>
> -----Original Message-----
> From: Jim McCaskey [mailto:jim.mccaskey@pervasive.com]
> Sent: Wednesday, March 25, 2009 10:17 PM
> To: 'users@maven.apache.org'
> Subject: How to perform a deploy only
>
> Hello all,
>
> I have several components all built from a top level pom. This works
> great for accelerating users to be able to build a lot of stuff quickly
> but is giving me some fits when trying to deploy. Up to this point I
> have been using deploy:deploy-file to get built components into our
> local repository after a full build is successful, but this is labor
> intensive.
>
> I would like to be able to run some variation of "mvn deploy" from the
> top level. I have figured out how to skip things using the FAQ here:
>
> http://maven.apache.org/plugins/maven-deploy-plugin/faq.html#skip
>
> But I do NOT want it to do anything other than deploy. I have googled
> for this but have not turned up anything useful. I was surprised that
> the documentation does not suggest how to do this. This is the correct
> deploy documentation I think.
>
> http://maven.apache.org/plugins/maven-deploy-plugin/
>
> Anyway, any help would be appreciated.
>
> Thanks!
>
> -Jim
>
>
> ---------------------------------------------------------------------
> 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: How to perform a deploy only
Posted by Kalle Korhonen <ka...@gmail.com>.
Hudson has a feature to deploy all after successful build rather than
module-by-module with native Maven.
Kalle
On Wed, Mar 25, 2009 at 8:25 PM, Jim McCaskey <ji...@pervasive.com>wrote:
> Thanks for the suggestion. I have been trying to avoid using repository
> managers for a number of reasons that are beyond the scope of this thread.
> I may have to break down eventually...
>
> I'm surprised no one has needed this sort of feature, or maybe they have
> and that's why Nexus has the features that it does. I was hoping to find a
> Maven native (whatever native means in a highly pluggable architecture) way
> to do this that would not take much additional work.
>
> mvn -DdoNothingButDeploy=true deploy
>
> That would be about perfect. :)
>
> Would this even be consider for an enhancement request if I opened it?
> Perhaps I am the only one interested in such a thing.
>
> Thanks!
>
> -Jim
>
> -----Original Message-----
> From: Edelson, Justin [mailto:Justin.Edelson@mtvstaff.com]
> Sent: Wednesday, March 25, 2009 9:55 PM
> To: Maven Users List
> Subject: RE: How to perform a deploy only
>
> Brian can pitch his own stuff far better than I can, but this kind of
> transactional deployment can be done with Nexus' Staging feature.
>
> I realized after I sent my deploy:deploy suggestion that it probably
> wouldn't work without running at least the package phase, sorry to give you
> bad info. I'm reasonably confident with some light hacking you could write a
> plugin that essentially faked the build, but if the below is your use case
> and you can afford Nexus Pro, it's probably a better solution.
>
> Justin
>
>
> ________________________________
>
> From: Jim McCaskey [mailto:jim.mccaskey@pervasive.com]
> Sent: Wed 3/25/2009 10:37 PM
> To: 'Maven Users List'
> Subject: RE: How to perform a deploy only
>
>
>
> I have a whole bunch of components that are mostly interrelated but
> consumable individually by downstream builds. If I run deploy it basically
> starts deploying as it goes, so if a downstream component breaks for some
> reason then I am left with half of the components updated in the maven repo
> and half not. That's not really what we want.
>
> So ideally, we would run a build/test, make sure it all gets through
> completely, then deploy the resulting artifacts.
>
> -Jim
>
> -----Original Message-----
> From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
> Sent: Wednesday, March 25, 2009 9:20 PM
> To: Maven Users List
> Subject: RE: How to perform a deploy only
>
> This really isn't a supported use case. Deploy is a phase and by
> definition all earlier phases run before the one you've asked for. Why
> would you not want to build before you deploy?
>
> -----Original Message-----
> From: Jim McCaskey [mailto:jim.mccaskey@pervasive.com]
> Sent: Wednesday, March 25, 2009 10:17 PM
> To: 'users@maven.apache.org'
> Subject: How to perform a deploy only
>
> Hello all,
>
> I have several components all built from a top level pom. This works
> great for accelerating users to be able to build a lot of stuff quickly
> but is giving me some fits when trying to deploy. Up to this point I
> have been using deploy:deploy-file to get built components into our
> local repository after a full build is successful, but this is labor
> intensive.
>
> I would like to be able to run some variation of "mvn deploy" from the
> top level. I have figured out how to skip things using the FAQ here:
>
> http://maven.apache.org/plugins/maven-deploy-plugin/faq.html#skip
>
> But I do NOT want it to do anything other than deploy. I have googled
> for this but have not turned up anything useful. I was surprised that
> the documentation does not suggest how to do this. This is the correct
> deploy documentation I think.
>
> http://maven.apache.org/plugins/maven-deploy-plugin/
>
> Anyway, any help would be appreciated.
>
> Thanks!
>
> -Jim
>
>
> ---------------------------------------------------------------------
> 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: How to perform a deploy only
Posted by Jim McCaskey <ji...@pervasive.com>.
With the minor caveat that I could never get mvn deploy:deploy to work at all. :) I had posted the error I was getting several days ago. Thanks for the suggestion though.
In any event, I like this solution a lot better the more I have used it. It prevents any and all accidental running of anything. It does not even make use of my existing pom's (they are not needed).
-Jim
-----Original Message-----
From: Stefan Seidel [mailto:sseidel@vub.de]
Sent: Monday, March 30, 2009 4:55 AM
To: users@maven.apache.org
Subject: Re: How to perform a deploy only
I still don't think your solution is easier than
mvn install
if not errorlevel 1 mvn deploy:deploy
But - everyone has their own solutions ;) Thanks for sharing.
Stefan
On Fri, 27 Mar 2009 13:17:43 -0500
Jim McCaskey <ji...@pervasive.com> wrote:
> Hi Stephen,
>
> Sure no problem. What I came up with was another set of posts, and was essentially following the advice you gave me a few days ago and some help from Dan Tran. That is, I use mvn deploy but output to a empty directory, then use a maven plugin to merge that to my primary repository.
>
> Here are some details (note I am using Maven 2.1.0 on Windows machines). So essentially I build like this:
>
> mvn -DaltDeploymentRepository=repo::default::file://E:\staging-repo deploy
>
> I then use the wagon-maven-plugin to merge this sparse area up to my corporate repository like this:
>
> mvn org.codehaus.mojo:wagon-maven-plugin:1.0-beta-1:merge-maven-repos -Dwagon.source=file://E:\staging-repo -Dwagon.target=file://\\server\share\mavenrepo -Djava.io.tmpdir=deploytemp
>
> Note that deploytemp is a directory that is created in the local directory. I can't seem to point it to a C:\temp for some reason, and really don't care. I just create the directory and use it. It's empty when it gets done. If you don't create that directory (or forget the java.io.tmpdir), you get a rather cryptic message about volume labels.
>
> I'm able to chain these two commands together after appropriate error checking in my automation server (IBM Rational Build Forge FWIW).
>
> So what I was after originally was a step for me to build, then another step to deploy only that I could use later on after everything was done. This accomplishes that goal, with a little help from the wagon-maven-plugin, and Dan Tran.
>
> Needless to say this methodology was not documented anywhere that I could find, so I am guessing that not many folks are interested in it. Frankly without the nudges in the right direction from this list, I would not have been able to figure it out. So thanks to everyone.
>
> -Jim
>
>
> -----Original Message-----
> From: Stephen Connolly [mailto:stephen.alan.connolly@gmail.com]
> Sent: Friday, March 27, 2009 12:45 PM
> To: Maven Users List
> Subject: Re: How to perform a deploy only
>
> Any chance you could post your solution?
>
> 2009/3/27 Jim McCaskey <ji...@pervasive.com>
>
> > I have found a solution that is working nicely. Having said that, I don't
> > think the request is that farfetched. When doing a deploy, you would
> > definitely want to make sure that all the components that made up the run
> > built successfully before deploying. Not doing so leaves your repository in
> > a corrupt state. Perhaps having the ability to delay the deploy phase until
> > all components are built/tested is what is needed, not necessarily a "Deploy
> > only" ability. In other words, run all other phases for all components,
> > then swing back through on a deploy run once all components are verified to
> > build/test.
> >
> > My guess would be that as more and more projects use Maven to glue
> > everything together, these sorts of things will come up more often.
> >
> > Anyway just a suggestion. Like I say, I have a solution that I'm happy
> > with.
> >
> > -Jim
> >
> > -----Original Message-----
> > From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
> > Sent: Thursday, March 26, 2009 9:43 PM
> > To: Maven Users List
> > Subject: RE: How to perform a deploy only
> >
> > Running the full lifecycle is a fundamental of Maven, so this type of
> > feature request is unlikely to gain traction. You should rather look at
> > your build configuration to solve the problem, or as mentioned use a
> > repo man that can help you out.
> >
> > -----Original Message-----
> > From: Jim McCaskey [mailto:jim.mccaskey@pervasive.com]
> > Sent: Wednesday, March 25, 2009 11:26 PM
> > To: 'Maven Users List'
> > Subject: RE: How to perform a deploy only
> >
> > Thanks for the suggestion. I have been trying to avoid using repository
> > managers for a number of reasons that are beyond the scope of this
> > thread. I may have to break down eventually...
> >
> > I'm surprised no one has needed this sort of feature, or maybe they have
> > and that's why Nexus has the features that it does. I was hoping to
> > find a Maven native (whatever native means in a highly pluggable
> > architecture) way to do this that would not take much additional work.
> >
> > mvn -DdoNothingButDeploy=true deploy
> >
> > That would be about perfect. :)
> >
> > Would this even be consider for an enhancement request if I opened it?
> > Perhaps I am the only one interested in such a thing.
> >
> > Thanks!
> >
> > -Jim
> >
> > -----Original Message-----
> > From: Edelson, Justin [mailto:Justin.Edelson@mtvstaff.com]
> > Sent: Wednesday, March 25, 2009 9:55 PM
> > To: Maven Users List
> > Subject: RE: How to perform a deploy only
> >
> > Brian can pitch his own stuff far better than I can, but this kind of
> > transactional deployment can be done with Nexus' Staging feature.
> >
> > I realized after I sent my deploy:deploy suggestion that it probably
> > wouldn't work without running at least the package phase, sorry to give
> > you bad info. I'm reasonably confident with some light hacking you could
> > write a plugin that essentially faked the build, but if the below is
> > your use case and you can afford Nexus Pro, it's probably a better
> > solution.
> >
> > Justin
> >
> >
> > ________________________________
> >
> > From: Jim McCaskey [mailto:jim.mccaskey@pervasive.com]
> > Sent: Wed 3/25/2009 10:37 PM
> > To: 'Maven Users List'
> > Subject: RE: How to perform a deploy only
> >
> >
> >
> > I have a whole bunch of components that are mostly interrelated but
> > consumable individually by downstream builds. If I run deploy it
> > basically starts deploying as it goes, so if a downstream component
> > breaks for some reason then I am left with half of the components
> > updated in the maven repo and half not. That's not really what we want.
> >
> > So ideally, we would run a build/test, make sure it all gets through
> > completely, then deploy the resulting artifacts.
> >
> > -Jim
> >
> > -----Original Message-----
> > From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
> > Sent: Wednesday, March 25, 2009 9:20 PM
> > To: Maven Users List
> > Subject: RE: How to perform a deploy only
> >
> > This really isn't a supported use case. Deploy is a phase and by
> > definition all earlier phases run before the one you've asked for. Why
> > would you not want to build before you deploy?
> >
> > -----Original Message-----
> > From: Jim McCaskey [mailto:jim.mccaskey@pervasive.com]
> > Sent: Wednesday, March 25, 2009 10:17 PM
> > To: 'users@maven.apache.org'
> > Subject: How to perform a deploy only
> >
> > Hello all,
> >
> > I have several components all built from a top level pom. This works
> > great for accelerating users to be able to build a lot of stuff quickly
> > but is giving me some fits when trying to deploy. Up to this point I
> > have been using deploy:deploy-file to get built components into our
> > local repository after a full build is successful, but this is labor
> > intensive.
> >
> > I would like to be able to run some variation of "mvn deploy" from the
> > top level. I have figured out how to skip things using the FAQ here:
> >
> > http://maven.apache.org/plugins/maven-deploy-plugin/faq.html#skip
> >
> > But I do NOT want it to do anything other than deploy. I have googled
> > for this but have not turned up anything useful. I was surprised that
> > the documentation does not suggest how to do this. This is the correct
> > deploy documentation I think.
> >
> > http://maven.apache.org/plugins/maven-deploy-plugin/
> >
> > Anyway, any help would be appreciated.
> >
> > Thanks!
> >
> > -Jim
> >
> >
> > ---------------------------------------------------------------------
> > 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
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > 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
>
--
Mit freundlichen Grüßen,
Stefan Seidel
Software-Entwickler
________________________
VUB Printmedia GmbH
Chopinstraße 4, 04103 Leipzig
tel. +49 (341) 9 60 50 93
fax. +49 (341) 9 60 50 92
mail. sseidel@vub.de
web. www.vub.de
VUB Printmedia GmbH
HRB Köln 24015
GF Dr. A. Preuss Neudorf, Dr. C. Preuss Neudorf
---------------------------------------------------------------------
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: How to perform a deploy only
Posted by Stephen Connolly <st...@gmail.com>.
Stefan,
The problem is that the deploy:deploy will be running in a separate reactor
and will be missing any attached artifacts from the reactor build.
So actually what you propose will completely fail for more than a
non-trivial build
-Stephen
2009/3/30 Stefan Seidel <ss...@vub.de>
> I still don't think your solution is easier than
>
> mvn install
> if not errorlevel 1 mvn deploy:deploy
>
> But - everyone has their own solutions ;) Thanks for sharing.
>
> Stefan
>
> On Fri, 27 Mar 2009 13:17:43 -0500
> Jim McCaskey <ji...@pervasive.com> wrote:
>
> > Hi Stephen,
> >
> > Sure no problem. What I came up with was another set of posts, and was
> essentially following the advice you gave me a few days ago and some help
> from Dan Tran. That is, I use mvn deploy but output to a empty directory,
> then use a maven plugin to merge that to my primary repository.
> >
> > Here are some details (note I am using Maven 2.1.0 on Windows machines).
> So essentially I build like this:
> >
> > mvn -DaltDeploymentRepository=repo::default::file://E:\staging-repo
> deploy
> >
> > I then use the wagon-maven-plugin to merge this sparse area up to my
> corporate repository like this:
> >
> > mvn org.codehaus.mojo:wagon-maven-plugin:1.0-beta-1:merge-maven-repos
> -Dwagon.source=file://E:\staging-repo
> -Dwagon.target=file://\\server\share\mavenrepo -Djava.io.tmpdir=deploytemp
> >
> > Note that deploytemp is a directory that is created in the local
> directory. I can't seem to point it to a C:\temp for some reason, and
> really don't care. I just create the directory and use it. It's empty when
> it gets done. If you don't create that directory (or forget the
> java.io.tmpdir), you get a rather cryptic message about volume labels.
> >
> > I'm able to chain these two commands together after appropriate error
> checking in my automation server (IBM Rational Build Forge FWIW).
> >
> > So what I was after originally was a step for me to build, then another
> step to deploy only that I could use later on after everything was done.
> This accomplishes that goal, with a little help from the
> wagon-maven-plugin, and Dan Tran.
> >
> > Needless to say this methodology was not documented anywhere that I could
> find, so I am guessing that not many folks are interested in it. Frankly
> without the nudges in the right direction from this list, I would not have
> been able to figure it out. So thanks to everyone.
> >
> > -Jim
> >
> >
> > -----Original Message-----
> > From: Stephen Connolly [mailto:stephen.alan.connolly@gmail.com]
> > Sent: Friday, March 27, 2009 12:45 PM
> > To: Maven Users List
> > Subject: Re: How to perform a deploy only
> >
> > Any chance you could post your solution?
> >
> > 2009/3/27 Jim McCaskey <ji...@pervasive.com>
> >
> > > I have found a solution that is working nicely. Having said that, I
> don't
> > > think the request is that farfetched. When doing a deploy, you would
> > > definitely want to make sure that all the components that made up the
> run
> > > built successfully before deploying. Not doing so leaves your
> repository in
> > > a corrupt state. Perhaps having the ability to delay the deploy phase
> until
> > > all components are built/tested is what is needed, not necessarily a
> "Deploy
> > > only" ability. In other words, run all other phases for all
> components,
> > > then swing back through on a deploy run once all components are
> verified to
> > > build/test.
> > >
> > > My guess would be that as more and more projects use Maven to glue
> > > everything together, these sorts of things will come up more often.
> > >
> > > Anyway just a suggestion. Like I say, I have a solution that I'm happy
> > > with.
> > >
> > > -Jim
> > >
> > > -----Original Message-----
> > > From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
> > > Sent: Thursday, March 26, 2009 9:43 PM
> > > To: Maven Users List
> > > Subject: RE: How to perform a deploy only
> > >
> > > Running the full lifecycle is a fundamental of Maven, so this type of
> > > feature request is unlikely to gain traction. You should rather look at
> > > your build configuration to solve the problem, or as mentioned use a
> > > repo man that can help you out.
> > >
> > > -----Original Message-----
> > > From: Jim McCaskey [mailto:jim.mccaskey@pervasive.com]
> > > Sent: Wednesday, March 25, 2009 11:26 PM
> > > To: 'Maven Users List'
> > > Subject: RE: How to perform a deploy only
> > >
> > > Thanks for the suggestion. I have been trying to avoid using
> repository
> > > managers for a number of reasons that are beyond the scope of this
> > > thread. I may have to break down eventually...
> > >
> > > I'm surprised no one has needed this sort of feature, or maybe they
> have
> > > and that's why Nexus has the features that it does. I was hoping to
> > > find a Maven native (whatever native means in a highly pluggable
> > > architecture) way to do this that would not take much additional work.
> > >
> > > mvn -DdoNothingButDeploy=true deploy
> > >
> > > That would be about perfect. :)
> > >
> > > Would this even be consider for an enhancement request if I opened it?
> > > Perhaps I am the only one interested in such a thing.
> > >
> > > Thanks!
> > >
> > > -Jim
> > >
> > > -----Original Message-----
> > > From: Edelson, Justin [mailto:Justin.Edelson@mtvstaff.com]
> > > Sent: Wednesday, March 25, 2009 9:55 PM
> > > To: Maven Users List
> > > Subject: RE: How to perform a deploy only
> > >
> > > Brian can pitch his own stuff far better than I can, but this kind of
> > > transactional deployment can be done with Nexus' Staging feature.
> > >
> > > I realized after I sent my deploy:deploy suggestion that it probably
> > > wouldn't work without running at least the package phase, sorry to give
> > > you bad info. I'm reasonably confident with some light hacking you
> could
> > > write a plugin that essentially faked the build, but if the below is
> > > your use case and you can afford Nexus Pro, it's probably a better
> > > solution.
> > >
> > > Justin
> > >
> > >
> > > ________________________________
> > >
> > > From: Jim McCaskey [mailto:jim.mccaskey@pervasive.com]
> > > Sent: Wed 3/25/2009 10:37 PM
> > > To: 'Maven Users List'
> > > Subject: RE: How to perform a deploy only
> > >
> > >
> > >
> > > I have a whole bunch of components that are mostly interrelated but
> > > consumable individually by downstream builds. If I run deploy it
> > > basically starts deploying as it goes, so if a downstream component
> > > breaks for some reason then I am left with half of the components
> > > updated in the maven repo and half not. That's not really what we
> want.
> > >
> > > So ideally, we would run a build/test, make sure it all gets through
> > > completely, then deploy the resulting artifacts.
> > >
> > > -Jim
> > >
> > > -----Original Message-----
> > > From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
> > > Sent: Wednesday, March 25, 2009 9:20 PM
> > > To: Maven Users List
> > > Subject: RE: How to perform a deploy only
> > >
> > > This really isn't a supported use case. Deploy is a phase and by
> > > definition all earlier phases run before the one you've asked for. Why
> > > would you not want to build before you deploy?
> > >
> > > -----Original Message-----
> > > From: Jim McCaskey [mailto:jim.mccaskey@pervasive.com]
> > > Sent: Wednesday, March 25, 2009 10:17 PM
> > > To: 'users@maven.apache.org'
> > > Subject: How to perform a deploy only
> > >
> > > Hello all,
> > >
> > > I have several components all built from a top level pom. This works
> > > great for accelerating users to be able to build a lot of stuff quickly
> > > but is giving me some fits when trying to deploy. Up to this point I
> > > have been using deploy:deploy-file to get built components into our
> > > local repository after a full build is successful, but this is labor
> > > intensive.
> > >
> > > I would like to be able to run some variation of "mvn deploy" from the
> > > top level. I have figured out how to skip things using the FAQ here:
> > >
> > > http://maven.apache.org/plugins/maven-deploy-plugin/faq.html#skip
> > >
> > > But I do NOT want it to do anything other than deploy. I have googled
> > > for this but have not turned up anything useful. I was surprised that
> > > the documentation does not suggest how to do this. This is the correct
> > > deploy documentation I think.
> > >
> > > http://maven.apache.org/plugins/maven-deploy-plugin/
> > >
> > > Anyway, any help would be appreciated.
> > >
> > > Thanks!
> > >
> > > -Jim
> > >
> > >
> > > ---------------------------------------------------------------------
> > > 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
> > >
> > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > 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
> >
>
>
> --
> Mit freundlichen Grüßen,
>
> Stefan Seidel
> Software-Entwickler
> ________________________
> VUB Printmedia GmbH
> Chopinstraße 4, 04103 Leipzig
> tel. +49 (341) 9 60 50 93
> fax. +49 (341) 9 60 50 92
> mail. sseidel@vub.de
> web. www.vub.de
>
> VUB Printmedia GmbH
> HRB Köln 24015
> GF Dr. A. Preuss Neudorf, Dr. C. Preuss Neudorf
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: How to perform a deploy only
Posted by Stefan Seidel <ss...@vub.de>.
I still don't think your solution is easier than
mvn install
if not errorlevel 1 mvn deploy:deploy
But - everyone has their own solutions ;) Thanks for sharing.
Stefan
On Fri, 27 Mar 2009 13:17:43 -0500
Jim McCaskey <ji...@pervasive.com> wrote:
> Hi Stephen,
>
> Sure no problem. What I came up with was another set of posts, and was essentially following the advice you gave me a few days ago and some help from Dan Tran. That is, I use mvn deploy but output to a empty directory, then use a maven plugin to merge that to my primary repository.
>
> Here are some details (note I am using Maven 2.1.0 on Windows machines). So essentially I build like this:
>
> mvn -DaltDeploymentRepository=repo::default::file://E:\staging-repo deploy
>
> I then use the wagon-maven-plugin to merge this sparse area up to my corporate repository like this:
>
> mvn org.codehaus.mojo:wagon-maven-plugin:1.0-beta-1:merge-maven-repos -Dwagon.source=file://E:\staging-repo -Dwagon.target=file://\\server\share\mavenrepo -Djava.io.tmpdir=deploytemp
>
> Note that deploytemp is a directory that is created in the local directory. I can't seem to point it to a C:\temp for some reason, and really don't care. I just create the directory and use it. It's empty when it gets done. If you don't create that directory (or forget the java.io.tmpdir), you get a rather cryptic message about volume labels.
>
> I'm able to chain these two commands together after appropriate error checking in my automation server (IBM Rational Build Forge FWIW).
>
> So what I was after originally was a step for me to build, then another step to deploy only that I could use later on after everything was done. This accomplishes that goal, with a little help from the wagon-maven-plugin, and Dan Tran.
>
> Needless to say this methodology was not documented anywhere that I could find, so I am guessing that not many folks are interested in it. Frankly without the nudges in the right direction from this list, I would not have been able to figure it out. So thanks to everyone.
>
> -Jim
>
>
> -----Original Message-----
> From: Stephen Connolly [mailto:stephen.alan.connolly@gmail.com]
> Sent: Friday, March 27, 2009 12:45 PM
> To: Maven Users List
> Subject: Re: How to perform a deploy only
>
> Any chance you could post your solution?
>
> 2009/3/27 Jim McCaskey <ji...@pervasive.com>
>
> > I have found a solution that is working nicely. Having said that, I don't
> > think the request is that farfetched. When doing a deploy, you would
> > definitely want to make sure that all the components that made up the run
> > built successfully before deploying. Not doing so leaves your repository in
> > a corrupt state. Perhaps having the ability to delay the deploy phase until
> > all components are built/tested is what is needed, not necessarily a "Deploy
> > only" ability. In other words, run all other phases for all components,
> > then swing back through on a deploy run once all components are verified to
> > build/test.
> >
> > My guess would be that as more and more projects use Maven to glue
> > everything together, these sorts of things will come up more often.
> >
> > Anyway just a suggestion. Like I say, I have a solution that I'm happy
> > with.
> >
> > -Jim
> >
> > -----Original Message-----
> > From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
> > Sent: Thursday, March 26, 2009 9:43 PM
> > To: Maven Users List
> > Subject: RE: How to perform a deploy only
> >
> > Running the full lifecycle is a fundamental of Maven, so this type of
> > feature request is unlikely to gain traction. You should rather look at
> > your build configuration to solve the problem, or as mentioned use a
> > repo man that can help you out.
> >
> > -----Original Message-----
> > From: Jim McCaskey [mailto:jim.mccaskey@pervasive.com]
> > Sent: Wednesday, March 25, 2009 11:26 PM
> > To: 'Maven Users List'
> > Subject: RE: How to perform a deploy only
> >
> > Thanks for the suggestion. I have been trying to avoid using repository
> > managers for a number of reasons that are beyond the scope of this
> > thread. I may have to break down eventually...
> >
> > I'm surprised no one has needed this sort of feature, or maybe they have
> > and that's why Nexus has the features that it does. I was hoping to
> > find a Maven native (whatever native means in a highly pluggable
> > architecture) way to do this that would not take much additional work.
> >
> > mvn -DdoNothingButDeploy=true deploy
> >
> > That would be about perfect. :)
> >
> > Would this even be consider for an enhancement request if I opened it?
> > Perhaps I am the only one interested in such a thing.
> >
> > Thanks!
> >
> > -Jim
> >
> > -----Original Message-----
> > From: Edelson, Justin [mailto:Justin.Edelson@mtvstaff.com]
> > Sent: Wednesday, March 25, 2009 9:55 PM
> > To: Maven Users List
> > Subject: RE: How to perform a deploy only
> >
> > Brian can pitch his own stuff far better than I can, but this kind of
> > transactional deployment can be done with Nexus' Staging feature.
> >
> > I realized after I sent my deploy:deploy suggestion that it probably
> > wouldn't work without running at least the package phase, sorry to give
> > you bad info. I'm reasonably confident with some light hacking you could
> > write a plugin that essentially faked the build, but if the below is
> > your use case and you can afford Nexus Pro, it's probably a better
> > solution.
> >
> > Justin
> >
> >
> > ________________________________
> >
> > From: Jim McCaskey [mailto:jim.mccaskey@pervasive.com]
> > Sent: Wed 3/25/2009 10:37 PM
> > To: 'Maven Users List'
> > Subject: RE: How to perform a deploy only
> >
> >
> >
> > I have a whole bunch of components that are mostly interrelated but
> > consumable individually by downstream builds. If I run deploy it
> > basically starts deploying as it goes, so if a downstream component
> > breaks for some reason then I am left with half of the components
> > updated in the maven repo and half not. That's not really what we want.
> >
> > So ideally, we would run a build/test, make sure it all gets through
> > completely, then deploy the resulting artifacts.
> >
> > -Jim
> >
> > -----Original Message-----
> > From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
> > Sent: Wednesday, March 25, 2009 9:20 PM
> > To: Maven Users List
> > Subject: RE: How to perform a deploy only
> >
> > This really isn't a supported use case. Deploy is a phase and by
> > definition all earlier phases run before the one you've asked for. Why
> > would you not want to build before you deploy?
> >
> > -----Original Message-----
> > From: Jim McCaskey [mailto:jim.mccaskey@pervasive.com]
> > Sent: Wednesday, March 25, 2009 10:17 PM
> > To: 'users@maven.apache.org'
> > Subject: How to perform a deploy only
> >
> > Hello all,
> >
> > I have several components all built from a top level pom. This works
> > great for accelerating users to be able to build a lot of stuff quickly
> > but is giving me some fits when trying to deploy. Up to this point I
> > have been using deploy:deploy-file to get built components into our
> > local repository after a full build is successful, but this is labor
> > intensive.
> >
> > I would like to be able to run some variation of "mvn deploy" from the
> > top level. I have figured out how to skip things using the FAQ here:
> >
> > http://maven.apache.org/plugins/maven-deploy-plugin/faq.html#skip
> >
> > But I do NOT want it to do anything other than deploy. I have googled
> > for this but have not turned up anything useful. I was surprised that
> > the documentation does not suggest how to do this. This is the correct
> > deploy documentation I think.
> >
> > http://maven.apache.org/plugins/maven-deploy-plugin/
> >
> > Anyway, any help would be appreciated.
> >
> > Thanks!
> >
> > -Jim
> >
> >
> > ---------------------------------------------------------------------
> > 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
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > 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
>
--
Mit freundlichen Grüßen,
Stefan Seidel
Software-Entwickler
________________________
VUB Printmedia GmbH
Chopinstraße 4, 04103 Leipzig
tel. +49 (341) 9 60 50 93
fax. +49 (341) 9 60 50 92
mail. sseidel@vub.de
web. www.vub.de
VUB Printmedia GmbH
HRB Köln 24015
GF Dr. A. Preuss Neudorf, Dr. C. Preuss Neudorf
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: How to perform a deploy only
Posted by Jim McCaskey <ji...@pervasive.com>.
Hi Stephen,
Sure no problem. What I came up with was another set of posts, and was essentially following the advice you gave me a few days ago and some help from Dan Tran. That is, I use mvn deploy but output to a empty directory, then use a maven plugin to merge that to my primary repository.
Here are some details (note I am using Maven 2.1.0 on Windows machines). So essentially I build like this:
mvn -DaltDeploymentRepository=repo::default::file://E:\staging-repo deploy
I then use the wagon-maven-plugin to merge this sparse area up to my corporate repository like this:
mvn org.codehaus.mojo:wagon-maven-plugin:1.0-beta-1:merge-maven-repos -Dwagon.source=file://E:\staging-repo -Dwagon.target=file://\\server\share\mavenrepo -Djava.io.tmpdir=deploytemp
Note that deploytemp is a directory that is created in the local directory. I can't seem to point it to a C:\temp for some reason, and really don't care. I just create the directory and use it. It's empty when it gets done. If you don't create that directory (or forget the java.io.tmpdir), you get a rather cryptic message about volume labels.
I'm able to chain these two commands together after appropriate error checking in my automation server (IBM Rational Build Forge FWIW).
So what I was after originally was a step for me to build, then another step to deploy only that I could use later on after everything was done. This accomplishes that goal, with a little help from the wagon-maven-plugin, and Dan Tran.
Needless to say this methodology was not documented anywhere that I could find, so I am guessing that not many folks are interested in it. Frankly without the nudges in the right direction from this list, I would not have been able to figure it out. So thanks to everyone.
-Jim
-----Original Message-----
From: Stephen Connolly [mailto:stephen.alan.connolly@gmail.com]
Sent: Friday, March 27, 2009 12:45 PM
To: Maven Users List
Subject: Re: How to perform a deploy only
Any chance you could post your solution?
2009/3/27 Jim McCaskey <ji...@pervasive.com>
> I have found a solution that is working nicely. Having said that, I don't
> think the request is that farfetched. When doing a deploy, you would
> definitely want to make sure that all the components that made up the run
> built successfully before deploying. Not doing so leaves your repository in
> a corrupt state. Perhaps having the ability to delay the deploy phase until
> all components are built/tested is what is needed, not necessarily a "Deploy
> only" ability. In other words, run all other phases for all components,
> then swing back through on a deploy run once all components are verified to
> build/test.
>
> My guess would be that as more and more projects use Maven to glue
> everything together, these sorts of things will come up more often.
>
> Anyway just a suggestion. Like I say, I have a solution that I'm happy
> with.
>
> -Jim
>
> -----Original Message-----
> From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
> Sent: Thursday, March 26, 2009 9:43 PM
> To: Maven Users List
> Subject: RE: How to perform a deploy only
>
> Running the full lifecycle is a fundamental of Maven, so this type of
> feature request is unlikely to gain traction. You should rather look at
> your build configuration to solve the problem, or as mentioned use a
> repo man that can help you out.
>
> -----Original Message-----
> From: Jim McCaskey [mailto:jim.mccaskey@pervasive.com]
> Sent: Wednesday, March 25, 2009 11:26 PM
> To: 'Maven Users List'
> Subject: RE: How to perform a deploy only
>
> Thanks for the suggestion. I have been trying to avoid using repository
> managers for a number of reasons that are beyond the scope of this
> thread. I may have to break down eventually...
>
> I'm surprised no one has needed this sort of feature, or maybe they have
> and that's why Nexus has the features that it does. I was hoping to
> find a Maven native (whatever native means in a highly pluggable
> architecture) way to do this that would not take much additional work.
>
> mvn -DdoNothingButDeploy=true deploy
>
> That would be about perfect. :)
>
> Would this even be consider for an enhancement request if I opened it?
> Perhaps I am the only one interested in such a thing.
>
> Thanks!
>
> -Jim
>
> -----Original Message-----
> From: Edelson, Justin [mailto:Justin.Edelson@mtvstaff.com]
> Sent: Wednesday, March 25, 2009 9:55 PM
> To: Maven Users List
> Subject: RE: How to perform a deploy only
>
> Brian can pitch his own stuff far better than I can, but this kind of
> transactional deployment can be done with Nexus' Staging feature.
>
> I realized after I sent my deploy:deploy suggestion that it probably
> wouldn't work without running at least the package phase, sorry to give
> you bad info. I'm reasonably confident with some light hacking you could
> write a plugin that essentially faked the build, but if the below is
> your use case and you can afford Nexus Pro, it's probably a better
> solution.
>
> Justin
>
>
> ________________________________
>
> From: Jim McCaskey [mailto:jim.mccaskey@pervasive.com]
> Sent: Wed 3/25/2009 10:37 PM
> To: 'Maven Users List'
> Subject: RE: How to perform a deploy only
>
>
>
> I have a whole bunch of components that are mostly interrelated but
> consumable individually by downstream builds. If I run deploy it
> basically starts deploying as it goes, so if a downstream component
> breaks for some reason then I am left with half of the components
> updated in the maven repo and half not. That's not really what we want.
>
> So ideally, we would run a build/test, make sure it all gets through
> completely, then deploy the resulting artifacts.
>
> -Jim
>
> -----Original Message-----
> From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
> Sent: Wednesday, March 25, 2009 9:20 PM
> To: Maven Users List
> Subject: RE: How to perform a deploy only
>
> This really isn't a supported use case. Deploy is a phase and by
> definition all earlier phases run before the one you've asked for. Why
> would you not want to build before you deploy?
>
> -----Original Message-----
> From: Jim McCaskey [mailto:jim.mccaskey@pervasive.com]
> Sent: Wednesday, March 25, 2009 10:17 PM
> To: 'users@maven.apache.org'
> Subject: How to perform a deploy only
>
> Hello all,
>
> I have several components all built from a top level pom. This works
> great for accelerating users to be able to build a lot of stuff quickly
> but is giving me some fits when trying to deploy. Up to this point I
> have been using deploy:deploy-file to get built components into our
> local repository after a full build is successful, but this is labor
> intensive.
>
> I would like to be able to run some variation of "mvn deploy" from the
> top level. I have figured out how to skip things using the FAQ here:
>
> http://maven.apache.org/plugins/maven-deploy-plugin/faq.html#skip
>
> But I do NOT want it to do anything other than deploy. I have googled
> for this but have not turned up anything useful. I was surprised that
> the documentation does not suggest how to do this. This is the correct
> deploy documentation I think.
>
> http://maven.apache.org/plugins/maven-deploy-plugin/
>
> Anyway, any help would be appreciated.
>
> Thanks!
>
> -Jim
>
>
> ---------------------------------------------------------------------
> 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
>
>
>
>
> ---------------------------------------------------------------------
> 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: How to perform a deploy only
Posted by Stephen Connolly <st...@gmail.com>.
Any chance you could post your solution?
2009/3/27 Jim McCaskey <ji...@pervasive.com>
> I have found a solution that is working nicely. Having said that, I don't
> think the request is that farfetched. When doing a deploy, you would
> definitely want to make sure that all the components that made up the run
> built successfully before deploying. Not doing so leaves your repository in
> a corrupt state. Perhaps having the ability to delay the deploy phase until
> all components are built/tested is what is needed, not necessarily a "Deploy
> only" ability. In other words, run all other phases for all components,
> then swing back through on a deploy run once all components are verified to
> build/test.
>
> My guess would be that as more and more projects use Maven to glue
> everything together, these sorts of things will come up more often.
>
> Anyway just a suggestion. Like I say, I have a solution that I'm happy
> with.
>
> -Jim
>
> -----Original Message-----
> From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
> Sent: Thursday, March 26, 2009 9:43 PM
> To: Maven Users List
> Subject: RE: How to perform a deploy only
>
> Running the full lifecycle is a fundamental of Maven, so this type of
> feature request is unlikely to gain traction. You should rather look at
> your build configuration to solve the problem, or as mentioned use a
> repo man that can help you out.
>
> -----Original Message-----
> From: Jim McCaskey [mailto:jim.mccaskey@pervasive.com]
> Sent: Wednesday, March 25, 2009 11:26 PM
> To: 'Maven Users List'
> Subject: RE: How to perform a deploy only
>
> Thanks for the suggestion. I have been trying to avoid using repository
> managers for a number of reasons that are beyond the scope of this
> thread. I may have to break down eventually...
>
> I'm surprised no one has needed this sort of feature, or maybe they have
> and that's why Nexus has the features that it does. I was hoping to
> find a Maven native (whatever native means in a highly pluggable
> architecture) way to do this that would not take much additional work.
>
> mvn -DdoNothingButDeploy=true deploy
>
> That would be about perfect. :)
>
> Would this even be consider for an enhancement request if I opened it?
> Perhaps I am the only one interested in such a thing.
>
> Thanks!
>
> -Jim
>
> -----Original Message-----
> From: Edelson, Justin [mailto:Justin.Edelson@mtvstaff.com]
> Sent: Wednesday, March 25, 2009 9:55 PM
> To: Maven Users List
> Subject: RE: How to perform a deploy only
>
> Brian can pitch his own stuff far better than I can, but this kind of
> transactional deployment can be done with Nexus' Staging feature.
>
> I realized after I sent my deploy:deploy suggestion that it probably
> wouldn't work without running at least the package phase, sorry to give
> you bad info. I'm reasonably confident with some light hacking you could
> write a plugin that essentially faked the build, but if the below is
> your use case and you can afford Nexus Pro, it's probably a better
> solution.
>
> Justin
>
>
> ________________________________
>
> From: Jim McCaskey [mailto:jim.mccaskey@pervasive.com]
> Sent: Wed 3/25/2009 10:37 PM
> To: 'Maven Users List'
> Subject: RE: How to perform a deploy only
>
>
>
> I have a whole bunch of components that are mostly interrelated but
> consumable individually by downstream builds. If I run deploy it
> basically starts deploying as it goes, so if a downstream component
> breaks for some reason then I am left with half of the components
> updated in the maven repo and half not. That's not really what we want.
>
> So ideally, we would run a build/test, make sure it all gets through
> completely, then deploy the resulting artifacts.
>
> -Jim
>
> -----Original Message-----
> From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
> Sent: Wednesday, March 25, 2009 9:20 PM
> To: Maven Users List
> Subject: RE: How to perform a deploy only
>
> This really isn't a supported use case. Deploy is a phase and by
> definition all earlier phases run before the one you've asked for. Why
> would you not want to build before you deploy?
>
> -----Original Message-----
> From: Jim McCaskey [mailto:jim.mccaskey@pervasive.com]
> Sent: Wednesday, March 25, 2009 10:17 PM
> To: 'users@maven.apache.org'
> Subject: How to perform a deploy only
>
> Hello all,
>
> I have several components all built from a top level pom. This works
> great for accelerating users to be able to build a lot of stuff quickly
> but is giving me some fits when trying to deploy. Up to this point I
> have been using deploy:deploy-file to get built components into our
> local repository after a full build is successful, but this is labor
> intensive.
>
> I would like to be able to run some variation of "mvn deploy" from the
> top level. I have figured out how to skip things using the FAQ here:
>
> http://maven.apache.org/plugins/maven-deploy-plugin/faq.html#skip
>
> But I do NOT want it to do anything other than deploy. I have googled
> for this but have not turned up anything useful. I was surprised that
> the documentation does not suggest how to do this. This is the correct
> deploy documentation I think.
>
> http://maven.apache.org/plugins/maven-deploy-plugin/
>
> Anyway, any help would be appreciated.
>
> Thanks!
>
> -Jim
>
>
> ---------------------------------------------------------------------
> 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
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
RE: How to perform a deploy only
Posted by Jim McCaskey <ji...@pervasive.com>.
I have found a solution that is working nicely. Having said that, I don't think the request is that farfetched. When doing a deploy, you would definitely want to make sure that all the components that made up the run built successfully before deploying. Not doing so leaves your repository in a corrupt state. Perhaps having the ability to delay the deploy phase until all components are built/tested is what is needed, not necessarily a "Deploy only" ability. In other words, run all other phases for all components, then swing back through on a deploy run once all components are verified to build/test.
My guess would be that as more and more projects use Maven to glue everything together, these sorts of things will come up more often.
Anyway just a suggestion. Like I say, I have a solution that I'm happy with.
-Jim
-----Original Message-----
From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
Sent: Thursday, March 26, 2009 9:43 PM
To: Maven Users List
Subject: RE: How to perform a deploy only
Running the full lifecycle is a fundamental of Maven, so this type of
feature request is unlikely to gain traction. You should rather look at
your build configuration to solve the problem, or as mentioned use a
repo man that can help you out.
-----Original Message-----
From: Jim McCaskey [mailto:jim.mccaskey@pervasive.com]
Sent: Wednesday, March 25, 2009 11:26 PM
To: 'Maven Users List'
Subject: RE: How to perform a deploy only
Thanks for the suggestion. I have been trying to avoid using repository
managers for a number of reasons that are beyond the scope of this
thread. I may have to break down eventually...
I'm surprised no one has needed this sort of feature, or maybe they have
and that's why Nexus has the features that it does. I was hoping to
find a Maven native (whatever native means in a highly pluggable
architecture) way to do this that would not take much additional work.
mvn -DdoNothingButDeploy=true deploy
That would be about perfect. :)
Would this even be consider for an enhancement request if I opened it?
Perhaps I am the only one interested in such a thing.
Thanks!
-Jim
-----Original Message-----
From: Edelson, Justin [mailto:Justin.Edelson@mtvstaff.com]
Sent: Wednesday, March 25, 2009 9:55 PM
To: Maven Users List
Subject: RE: How to perform a deploy only
Brian can pitch his own stuff far better than I can, but this kind of
transactional deployment can be done with Nexus' Staging feature.
I realized after I sent my deploy:deploy suggestion that it probably
wouldn't work without running at least the package phase, sorry to give
you bad info. I'm reasonably confident with some light hacking you could
write a plugin that essentially faked the build, but if the below is
your use case and you can afford Nexus Pro, it's probably a better
solution.
Justin
________________________________
From: Jim McCaskey [mailto:jim.mccaskey@pervasive.com]
Sent: Wed 3/25/2009 10:37 PM
To: 'Maven Users List'
Subject: RE: How to perform a deploy only
I have a whole bunch of components that are mostly interrelated but
consumable individually by downstream builds. If I run deploy it
basically starts deploying as it goes, so if a downstream component
breaks for some reason then I am left with half of the components
updated in the maven repo and half not. That's not really what we want.
So ideally, we would run a build/test, make sure it all gets through
completely, then deploy the resulting artifacts.
-Jim
-----Original Message-----
From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
Sent: Wednesday, March 25, 2009 9:20 PM
To: Maven Users List
Subject: RE: How to perform a deploy only
This really isn't a supported use case. Deploy is a phase and by
definition all earlier phases run before the one you've asked for. Why
would you not want to build before you deploy?
-----Original Message-----
From: Jim McCaskey [mailto:jim.mccaskey@pervasive.com]
Sent: Wednesday, March 25, 2009 10:17 PM
To: 'users@maven.apache.org'
Subject: How to perform a deploy only
Hello all,
I have several components all built from a top level pom. This works
great for accelerating users to be able to build a lot of stuff quickly
but is giving me some fits when trying to deploy. Up to this point I
have been using deploy:deploy-file to get built components into our
local repository after a full build is successful, but this is labor
intensive.
I would like to be able to run some variation of "mvn deploy" from the
top level. I have figured out how to skip things using the FAQ here:
http://maven.apache.org/plugins/maven-deploy-plugin/faq.html#skip
But I do NOT want it to do anything other than deploy. I have googled
for this but have not turned up anything useful. I was surprised that
the documentation does not suggest how to do this. This is the correct
deploy documentation I think.
http://maven.apache.org/plugins/maven-deploy-plugin/
Anyway, any help would be appreciated.
Thanks!
-Jim
---------------------------------------------------------------------
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
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: How to perform a deploy only
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
Running the full lifecycle is a fundamental of Maven, so this type of
feature request is unlikely to gain traction. You should rather look at
your build configuration to solve the problem, or as mentioned use a
repo man that can help you out.
-----Original Message-----
From: Jim McCaskey [mailto:jim.mccaskey@pervasive.com]
Sent: Wednesday, March 25, 2009 11:26 PM
To: 'Maven Users List'
Subject: RE: How to perform a deploy only
Thanks for the suggestion. I have been trying to avoid using repository
managers for a number of reasons that are beyond the scope of this
thread. I may have to break down eventually...
I'm surprised no one has needed this sort of feature, or maybe they have
and that's why Nexus has the features that it does. I was hoping to
find a Maven native (whatever native means in a highly pluggable
architecture) way to do this that would not take much additional work.
mvn -DdoNothingButDeploy=true deploy
That would be about perfect. :)
Would this even be consider for an enhancement request if I opened it?
Perhaps I am the only one interested in such a thing.
Thanks!
-Jim
-----Original Message-----
From: Edelson, Justin [mailto:Justin.Edelson@mtvstaff.com]
Sent: Wednesday, March 25, 2009 9:55 PM
To: Maven Users List
Subject: RE: How to perform a deploy only
Brian can pitch his own stuff far better than I can, but this kind of
transactional deployment can be done with Nexus' Staging feature.
I realized after I sent my deploy:deploy suggestion that it probably
wouldn't work without running at least the package phase, sorry to give
you bad info. I'm reasonably confident with some light hacking you could
write a plugin that essentially faked the build, but if the below is
your use case and you can afford Nexus Pro, it's probably a better
solution.
Justin
________________________________
From: Jim McCaskey [mailto:jim.mccaskey@pervasive.com]
Sent: Wed 3/25/2009 10:37 PM
To: 'Maven Users List'
Subject: RE: How to perform a deploy only
I have a whole bunch of components that are mostly interrelated but
consumable individually by downstream builds. If I run deploy it
basically starts deploying as it goes, so if a downstream component
breaks for some reason then I am left with half of the components
updated in the maven repo and half not. That's not really what we want.
So ideally, we would run a build/test, make sure it all gets through
completely, then deploy the resulting artifacts.
-Jim
-----Original Message-----
From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
Sent: Wednesday, March 25, 2009 9:20 PM
To: Maven Users List
Subject: RE: How to perform a deploy only
This really isn't a supported use case. Deploy is a phase and by
definition all earlier phases run before the one you've asked for. Why
would you not want to build before you deploy?
-----Original Message-----
From: Jim McCaskey [mailto:jim.mccaskey@pervasive.com]
Sent: Wednesday, March 25, 2009 10:17 PM
To: 'users@maven.apache.org'
Subject: How to perform a deploy only
Hello all,
I have several components all built from a top level pom. This works
great for accelerating users to be able to build a lot of stuff quickly
but is giving me some fits when trying to deploy. Up to this point I
have been using deploy:deploy-file to get built components into our
local repository after a full build is successful, but this is labor
intensive.
I would like to be able to run some variation of "mvn deploy" from the
top level. I have figured out how to skip things using the FAQ here:
http://maven.apache.org/plugins/maven-deploy-plugin/faq.html#skip
But I do NOT want it to do anything other than deploy. I have googled
for this but have not turned up anything useful. I was surprised that
the documentation does not suggest how to do this. This is the correct
deploy documentation I think.
http://maven.apache.org/plugins/maven-deploy-plugin/
Anyway, any help would be appreciated.
Thanks!
-Jim
---------------------------------------------------------------------
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: How to perform a deploy only
Posted by Jim McCaskey <ji...@pervasive.com>.
Thanks for the suggestion. I have been trying to avoid using repository managers for a number of reasons that are beyond the scope of this thread. I may have to break down eventually...
I'm surprised no one has needed this sort of feature, or maybe they have and that's why Nexus has the features that it does. I was hoping to find a Maven native (whatever native means in a highly pluggable architecture) way to do this that would not take much additional work.
mvn -DdoNothingButDeploy=true deploy
That would be about perfect. :)
Would this even be consider for an enhancement request if I opened it? Perhaps I am the only one interested in such a thing.
Thanks!
-Jim
-----Original Message-----
From: Edelson, Justin [mailto:Justin.Edelson@mtvstaff.com]
Sent: Wednesday, March 25, 2009 9:55 PM
To: Maven Users List
Subject: RE: How to perform a deploy only
Brian can pitch his own stuff far better than I can, but this kind of transactional deployment can be done with Nexus' Staging feature.
I realized after I sent my deploy:deploy suggestion that it probably wouldn't work without running at least the package phase, sorry to give you bad info. I'm reasonably confident with some light hacking you could write a plugin that essentially faked the build, but if the below is your use case and you can afford Nexus Pro, it's probably a better solution.
Justin
________________________________
From: Jim McCaskey [mailto:jim.mccaskey@pervasive.com]
Sent: Wed 3/25/2009 10:37 PM
To: 'Maven Users List'
Subject: RE: How to perform a deploy only
I have a whole bunch of components that are mostly interrelated but consumable individually by downstream builds. If I run deploy it basically starts deploying as it goes, so if a downstream component breaks for some reason then I am left with half of the components updated in the maven repo and half not. That's not really what we want.
So ideally, we would run a build/test, make sure it all gets through completely, then deploy the resulting artifacts.
-Jim
-----Original Message-----
From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
Sent: Wednesday, March 25, 2009 9:20 PM
To: Maven Users List
Subject: RE: How to perform a deploy only
This really isn't a supported use case. Deploy is a phase and by
definition all earlier phases run before the one you've asked for. Why
would you not want to build before you deploy?
-----Original Message-----
From: Jim McCaskey [mailto:jim.mccaskey@pervasive.com]
Sent: Wednesday, March 25, 2009 10:17 PM
To: 'users@maven.apache.org'
Subject: How to perform a deploy only
Hello all,
I have several components all built from a top level pom. This works
great for accelerating users to be able to build a lot of stuff quickly
but is giving me some fits when trying to deploy. Up to this point I
have been using deploy:deploy-file to get built components into our
local repository after a full build is successful, but this is labor
intensive.
I would like to be able to run some variation of "mvn deploy" from the
top level. I have figured out how to skip things using the FAQ here:
http://maven.apache.org/plugins/maven-deploy-plugin/faq.html#skip
But I do NOT want it to do anything other than deploy. I have googled
for this but have not turned up anything useful. I was surprised that
the documentation does not suggest how to do this. This is the correct
deploy documentation I think.
http://maven.apache.org/plugins/maven-deploy-plugin/
Anyway, any help would be appreciated.
Thanks!
-Jim
---------------------------------------------------------------------
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: How to perform a deploy only
Posted by "Edelson, Justin" <Ju...@mtvstaff.com>.
Brian can pitch his own stuff far better than I can, but this kind of transactional deployment can be done with Nexus' Staging feature.
I realized after I sent my deploy:deploy suggestion that it probably wouldn't work without running at least the package phase, sorry to give you bad info. I'm reasonably confident with some light hacking you could write a plugin that essentially faked the build, but if the below is your use case and you can afford Nexus Pro, it's probably a better solution.
Justin
________________________________
From: Jim McCaskey [mailto:jim.mccaskey@pervasive.com]
Sent: Wed 3/25/2009 10:37 PM
To: 'Maven Users List'
Subject: RE: How to perform a deploy only
I have a whole bunch of components that are mostly interrelated but consumable individually by downstream builds. If I run deploy it basically starts deploying as it goes, so if a downstream component breaks for some reason then I am left with half of the components updated in the maven repo and half not. That's not really what we want.
So ideally, we would run a build/test, make sure it all gets through completely, then deploy the resulting artifacts.
-Jim
-----Original Message-----
From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
Sent: Wednesday, March 25, 2009 9:20 PM
To: Maven Users List
Subject: RE: How to perform a deploy only
This really isn't a supported use case. Deploy is a phase and by
definition all earlier phases run before the one you've asked for. Why
would you not want to build before you deploy?
-----Original Message-----
From: Jim McCaskey [mailto:jim.mccaskey@pervasive.com]
Sent: Wednesday, March 25, 2009 10:17 PM
To: 'users@maven.apache.org'
Subject: How to perform a deploy only
Hello all,
I have several components all built from a top level pom. This works
great for accelerating users to be able to build a lot of stuff quickly
but is giving me some fits when trying to deploy. Up to this point I
have been using deploy:deploy-file to get built components into our
local repository after a full build is successful, but this is labor
intensive.
I would like to be able to run some variation of "mvn deploy" from the
top level. I have figured out how to skip things using the FAQ here:
http://maven.apache.org/plugins/maven-deploy-plugin/faq.html#skip
But I do NOT want it to do anything other than deploy. I have googled
for this but have not turned up anything useful. I was surprised that
the documentation does not suggest how to do this. This is the correct
deploy documentation I think.
http://maven.apache.org/plugins/maven-deploy-plugin/
Anyway, any help would be appreciated.
Thanks!
-Jim
---------------------------------------------------------------------
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: How to perform a deploy only
Posted by Stefan Seidel <ss...@vub.de>.
I don't really see the problem here.
mvn clean install && mvn deploy:deploy
I'm sure there is an equivalent if you're building under Windows.
Stefan
On Wed, 25 Mar 2009 21:37:29 -0500
Jim McCaskey <ji...@pervasive.com> wrote:
> I have a whole bunch of components that are mostly interrelated but consumable individually by downstream builds. If I run deploy it basically starts deploying as it goes, so if a downstream component breaks for some reason then I am left with half of the components updated in the maven repo and half not. That's not really what we want.
>
> So ideally, we would run a build/test, make sure it all gets through completely, then deploy the resulting artifacts.
>
> -Jim
>
> -----Original Message-----
> From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
> Sent: Wednesday, March 25, 2009 9:20 PM
> To: Maven Users List
> Subject: RE: How to perform a deploy only
>
> This really isn't a supported use case. Deploy is a phase and by
> definition all earlier phases run before the one you've asked for. Why
> would you not want to build before you deploy?
>
> -----Original Message-----
> From: Jim McCaskey [mailto:jim.mccaskey@pervasive.com]
> Sent: Wednesday, March 25, 2009 10:17 PM
> To: 'users@maven.apache.org'
> Subject: How to perform a deploy only
>
> Hello all,
>
> I have several components all built from a top level pom. This works
> great for accelerating users to be able to build a lot of stuff quickly
> but is giving me some fits when trying to deploy. Up to this point I
> have been using deploy:deploy-file to get built components into our
> local repository after a full build is successful, but this is labor
> intensive.
>
> I would like to be able to run some variation of "mvn deploy" from the
> top level. I have figured out how to skip things using the FAQ here:
>
> http://maven.apache.org/plugins/maven-deploy-plugin/faq.html#skip
>
> But I do NOT want it to do anything other than deploy. I have googled
> for this but have not turned up anything useful. I was surprised that
> the documentation does not suggest how to do this. This is the correct
> deploy documentation I think.
>
> http://maven.apache.org/plugins/maven-deploy-plugin/
>
> Anyway, any help would be appreciated.
>
> Thanks!
>
> -Jim
>
>
> ---------------------------------------------------------------------
> 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
>
--
Mit freundlichen Grüßen,
Stefan Seidel
Software-Entwickler
________________________
VUB Printmedia GmbH
Chopinstraße 4, 04103 Leipzig
tel. +49 (341) 9 60 50 93
fax. +49 (341) 9 60 50 92
mail. sseidel@vub.de
web. www.vub.de
VUB Printmedia GmbH
HRB Köln 24015
GF Dr. A. Preuss Neudorf, Dr. C. Preuss Neudorf
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: How to perform a deploy only
Posted by Jim McCaskey <ji...@pervasive.com>.
I have a whole bunch of components that are mostly interrelated but consumable individually by downstream builds. If I run deploy it basically starts deploying as it goes, so if a downstream component breaks for some reason then I am left with half of the components updated in the maven repo and half not. That's not really what we want.
So ideally, we would run a build/test, make sure it all gets through completely, then deploy the resulting artifacts.
-Jim
-----Original Message-----
From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
Sent: Wednesday, March 25, 2009 9:20 PM
To: Maven Users List
Subject: RE: How to perform a deploy only
This really isn't a supported use case. Deploy is a phase and by
definition all earlier phases run before the one you've asked for. Why
would you not want to build before you deploy?
-----Original Message-----
From: Jim McCaskey [mailto:jim.mccaskey@pervasive.com]
Sent: Wednesday, March 25, 2009 10:17 PM
To: 'users@maven.apache.org'
Subject: How to perform a deploy only
Hello all,
I have several components all built from a top level pom. This works
great for accelerating users to be able to build a lot of stuff quickly
but is giving me some fits when trying to deploy. Up to this point I
have been using deploy:deploy-file to get built components into our
local repository after a full build is successful, but this is labor
intensive.
I would like to be able to run some variation of "mvn deploy" from the
top level. I have figured out how to skip things using the FAQ here:
http://maven.apache.org/plugins/maven-deploy-plugin/faq.html#skip
But I do NOT want it to do anything other than deploy. I have googled
for this but have not turned up anything useful. I was surprised that
the documentation does not suggest how to do this. This is the correct
deploy documentation I think.
http://maven.apache.org/plugins/maven-deploy-plugin/
Anyway, any help would be appreciated.
Thanks!
-Jim
---------------------------------------------------------------------
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: How to perform a deploy only
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
This really isn't a supported use case. Deploy is a phase and by
definition all earlier phases run before the one you've asked for. Why
would you not want to build before you deploy?
-----Original Message-----
From: Jim McCaskey [mailto:jim.mccaskey@pervasive.com]
Sent: Wednesday, March 25, 2009 10:17 PM
To: 'users@maven.apache.org'
Subject: How to perform a deploy only
Hello all,
I have several components all built from a top level pom. This works
great for accelerating users to be able to build a lot of stuff quickly
but is giving me some fits when trying to deploy. Up to this point I
have been using deploy:deploy-file to get built components into our
local repository after a full build is successful, but this is labor
intensive.
I would like to be able to run some variation of "mvn deploy" from the
top level. I have figured out how to skip things using the FAQ here:
http://maven.apache.org/plugins/maven-deploy-plugin/faq.html#skip
But I do NOT want it to do anything other than deploy. I have googled
for this but have not turned up anything useful. I was surprised that
the documentation does not suggest how to do this. This is the correct
deploy documentation I think.
http://maven.apache.org/plugins/maven-deploy-plugin/
Anyway, any help would be appreciated.
Thanks!
-Jim
---------------------------------------------------------------------
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: How to perform a deploy only
Posted by Jim McCaskey <ji...@pervasive.com>.
Hi Justin,
Thanks for the suggestion. I just tried your suggestion and got this error:
[INFO] [deploy:deploy]
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] The packaging for this project did not assign a file to the build artifact
I guess it's not getting enough data from the rest of the Maven phases as Brian suggests in his other message to get all the data it needs on which files to deploy.
-Jim
-----Original Message-----
From: Edelson, Justin [mailto:Justin.Edelson@mtvstaff.com]
Sent: Wednesday, March 25, 2009 9:21 PM
To: Maven Users List
Subject: RE: How to perform a deploy only
I'm not 100% sure I understand, but "mvn deploy:deploy" will do what I think you are describing.
Justin
________________________________
From: Jim McCaskey [mailto:jim.mccaskey@pervasive.com]
Sent: Wed 3/25/2009 10:17 PM
To: 'users@maven.apache.org'
Subject: How to perform a deploy only
Hello all,
I have several components all built from a top level pom. This works great for accelerating users to be able to build a lot of stuff quickly but is giving me some fits when trying to deploy. Up to this point I have been using deploy:deploy-file to get built components into our local repository after a full build is successful, but this is labor intensive.
I would like to be able to run some variation of "mvn deploy" from the top level. I have figured out how to skip things using the FAQ here:
http://maven.apache.org/plugins/maven-deploy-plugin/faq.html#skip
But I do NOT want it to do anything other than deploy. I have googled for this but have not turned up anything useful. I was surprised that the documentation does not suggest how to do this. This is the correct deploy documentation I think.
http://maven.apache.org/plugins/maven-deploy-plugin/
Anyway, any help would be appreciated.
Thanks!
-Jim
---------------------------------------------------------------------
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: How to perform a deploy only
Posted by "Edelson, Justin" <Ju...@mtvstaff.com>.
I'm not 100% sure I understand, but "mvn deploy:deploy" will do what I think you are describing.
Justin
________________________________
From: Jim McCaskey [mailto:jim.mccaskey@pervasive.com]
Sent: Wed 3/25/2009 10:17 PM
To: 'users@maven.apache.org'
Subject: How to perform a deploy only
Hello all,
I have several components all built from a top level pom. This works great for accelerating users to be able to build a lot of stuff quickly but is giving me some fits when trying to deploy. Up to this point I have been using deploy:deploy-file to get built components into our local repository after a full build is successful, but this is labor intensive.
I would like to be able to run some variation of "mvn deploy" from the top level. I have figured out how to skip things using the FAQ here:
http://maven.apache.org/plugins/maven-deploy-plugin/faq.html#skip
But I do NOT want it to do anything other than deploy. I have googled for this but have not turned up anything useful. I was surprised that the documentation does not suggest how to do this. This is the correct deploy documentation I think.
http://maven.apache.org/plugins/maven-deploy-plugin/
Anyway, any help would be appreciated.
Thanks!
-Jim
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: How to perform a deploy only
Posted by David Weintraub <qa...@gmail.com>.
On Wed, Mar 25, 2009 at 10:17 PM, Jim McCaskey
<ji...@pervasive.com> wrote:
> Hello all,
>
> I have several components all built from a top level pom. This
> works great for accelerating users to be able to build a lot of stuff
> quickly but is giving me some fits when trying to deploy. Up to
> this point I have been using deploy:deploy-file to get built
> components into our local repository after a full build is
> successful, but this is labor intensive.
Have you looked at the Promotion Plugin? It looks like it does exactly
what you want.
When you set up a promotion, you can have it triggered manually, or
when a certain set of downstream artifacts get deployed. You can then
have it email you, do tagging, or deploy your artifacts to the Maven
repository.
--
David Weintraub
qazwart@gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: How to perform a deploy only
Posted by Francois MAROT <fr...@gmail.com>.
Hello Pavan,
it's hard to tell exactly but in Eclipse (Eclipse JEE at least) if you
declare a tomcat instance in the "server" window, and import your maven
modules with m2e, you should be able to deploy to Tomcat without problems.
No more needs for command-line clean/install/deploy (as long as your project
does not do very dirty stuffs).
Check the "m2e-wtp" keyword on Google as it's the plugin doing the bridge
between Maven in Eclipse and the server deployment stuffs...
--
View this message in context: http://maven.40175.n5.nabble.com/How-to-perform-a-deploy-only-tp118100p5851470.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