*that* deploy has actually nothing to do with the deploy you want. It's only and specifically designed to push a binary produced by the building process to some maven repository manager (say archiva, nexus or artifactory for example).
2014-09-10 17:07 GMT+02:00 Jan <[email protected]>: > Thanks All. > > My package is not environment specific, and currently i compile and package > using Maven, and run deployment using Ant, coz when i tried to run maven > deploy it was using the full life cycle goals again, instead of this is > there any way to execute just deploy and skip all other goals? > > > On Wed, Sep 10, 2014 at 9:26 AM, Graham Leggett <[email protected]> wrote: > > > On 10 Sep 2014, at 10:03, Jan <[email protected]> wrote: > > > > > Does anyone using Maven as Build Once and deploy Everywhere method? > Like > > > lets say i don't want to recompile my source code everytime for > different > > > environment DEV,SIT,UAT & PROD. I want to do my compile and package > only > > at > > > DEV then deploy the artifact to all mentioned environment. Is this > > possible > > > using Maven, is there any reference any one could share with me Please. > > > > We do this extensively with maven, using the maven release plugin. > > > > Our artifacts are in turn installable packages (rpms in our case, but > > could be deb, whatever) which get published into a yum repository. > > > > The code is "promoted" from dev to test to higher environments by hard > > linking the packages into distinct yum repos, a yum repo for each > > environment. > > > > The release created by the release plugin is built just once and > promoted. > > The rpms are created using the rpm-maven-plugin. > > > > Regards, > > Graham > > -- > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > > > -- > Baptiste <Batmat> MATHUS - http://batmat.net > Sauvez un arbre, > Mangez un castor ! nbsp;! >
