Re: [ee4j-build] Parent pom 1.0.5 released

[Tomas Kraus <tomas.kraus@xxxxxxxxxx>]

Hi Romain,

here is the script.

There is still one thing only in my TODO list - routine to drop old 
deployments with the same comment (GroipId:ArtifactId:Version). I'm 
doing it manually.

I'm not using simple deploy from historical reasons - we had some issues 
in Metro project with it. Current sequence seems to work fine in all our 
projects.

But if simple deploy works for particular project, it should be used.

Tomas

Dne 13.11.18 v 1:36 Romain Grecourt napsal(a):
> Tomas can you point me at this script ? I'd like to review it.
>
> Why are we invoking plugins directly and not using the deploy phase ?
> With the current configuration in the parent pom there should be no 
> magic required. A simple "mvn deploy -Possrh-release" should just work.
>
> On 11/12/18 12:41 PM, Tomas Kraus wrote:
> > With 1.0.5 parent deploy target will go trough nexux plugin and close 
> > deployment. If you are using copy of my scripts, replace 
> > MVN_DEPLOY_ARGS='deploy:deploy' with 
> > MVN_DEPLOY_ARGS='nexus-staging:deploy' and it will work too.
>
> _______________________________________________
> ee4j-build mailing list
> ee4j-build@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or 
> unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/ee4j-build

Attachment: release.sh
Description: Bourne shell script