[jbosstools-dev] New mechanism for target=platforms

[Mickael Istria]

Hi all,

We'd like to provide an improvement to target-platform management that 
would make them more reliable, thanks to more validation, and more 
automation (less manual error-prone maintainance).
The first step consists in this bug: 
https://issues.jboss.org/browse/JBIDE-12565
The idea is to automatically generate unified.target and local.target 
from multiple.target. Also, we'll split the target-platforms in several 
maven artifacts (GAVs), so that we can publish them more incrementally 
and perform much more validation to guarantee that what is published is 
always synchronized with our sites.
Artifact and group IDs for target-platform will change. However, 
profiles will be updated in parent pom to use those new artifacts, so 
you should not be affected by this change, but since Target Platform are 
a central component, it may cause a bad day if things go worse than 
expected.

The plan is the following:
Step 1: I set up the CI job for this new mechanism (since artifact 
changed it won't collide with current platforms). Publication of the 
aggregated target site will still be done by previous job.
Step 2: when we are in a good state, remove publication of aggregated 
target site from current job and move it to the new one
Step 3: when we are in a good state, change profiles in parent pom to 
use new targets
Step 4: remove old jobs from Jenkins and old target-platform mechanism 
from SVN.
Step 5: there's no step 5.

I'll start tomorrow with Step 1, the goal is to have all this finished 
for Tuesday (before code-freeze).

Please share any concern.
Cheers,
-- 
Mickael Istria
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com> - My Tweets 
<http://twitter.com/mickaelistria>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20120912/c74aebe1/attachment.html