| Re: [bpel-dev] Update sites and Builds |
|
Hi Neto, Le 05/04/2012 11:01, Neto a écrit : Well, OK, but with which platform? JBoss Tools needs a build against Helios. Petals Studio needs a build against Indigo, but the Helios version works on Indigo. And the next official release is built against Juno. Helios builds are done on every commit. Juno builds are launched manually. These builds are packed and signed (as defined by the Eclipse release process), which takes longer. Next year, there will be another platform. And this is just about the builds. We need one update site for the releases, and one for the snapshots. Besides, the BPEL Designer has moved into the SOA top-level project. So, the final update site must be under "soa" and not "technology" anymore. My questions were about clearing the way it should work. :) I proposed one location per platform / build job, plus one location for the promoted builds (under "soa"), pushed manually and for the last platform only (Juno this year). Previous promoted update sites should be moved to archive.eclipse.org. 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 |