Re: [bpel-dev] Update sites and Builds

[Vincent Zurczak <vincent.zurczak@xxxxxxxxxxxxxx>]

OK for the versioned solution.
But concretely?


Le 05/04/2012 17:22, Mickael Istria a écrit :

Maybe we could think of using a 0.6.0/snapshots repository, and then when a build get ready to go to a juno milestone, copy it into 0.6.0/milestone repo, and when a build gets ready to be released, copy it into 0.6.0/releases repository.

On 04/05/2012 05:19 PM, Bob Brodt wrote:

Works for me. Does this cause any problems with the builds targeted for juno between now and its scheduled release date?

Actually, we are in version 0.8.0 (the Hudson job should be renamed).
OK for the promotion mechanism. But we have to do it manually, right? That's fine with me.

We have one job for Helios (bpel-0.5) and one for Juno (-juno). We must keep one job per platform to make sure it builds and works.
For the moment, packing and signing is done with Maven, in the Juno build.

What changes do you propose?
Which job will pack, sign and publish the snapshot update site?

           Vincent.

--
Vincent Zurczak

RCP Developer & ESB Consultant
Petals Link: http://www.petalslink.com
My Blog: http://vzurczak.wordpress.com
+33 (0) 4 76 96 15 16