Re: [cbi-dev] Release schedule

[Mikael Barbero <mikael@xxxxxxxxxxx>]

The issue is that I don't think it is a good idea to sign the jars with itself. I would rather use the signing webservice directly.

Le 30 avr. 2015 à 10:20, Mickael Istria <mistria@xxxxxxxxxx> a écrit :

On 04/30/2015 10:10 AM, Mikael Barbero wrote:

Then, I would love to see this change https://git.eclipse.org/r/#/c/46751/ being reviewed. It removes the chicken and egg issue of using the previous version of jarsigner to sign jarsigner and other CBI maven plugins. The idea is rather to sign the jars after a "mvn clean verify" with the following script:

You could keep the current block but use the ${project.version} instead of previous one, and run sequentially
$ mvn install
$ mvn deploy -Prelease
when deploying. It seems easier to me than maintaining a piece of shell.

--
Mickael Istria
Eclipse developer at JBoss, by Red Hat
My blog - My Tweets

_______________________________________________
cbi-dev mailing list
cbi-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cbi-dev