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.conno...@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 <jim.mccas...@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.edel...@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.mccas...@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:bri...@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.mccas...@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-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Reply via email to