[
https://issues.jboss.org/browse/JBIDE-12565?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-12565:
----------------------------------------
Your new approach will bootstrap [2] with IUs, then run validation to
see if everything needed by the TP is in fact on the TP site, including the need for
multiple versions of IUs (we already had lucene.core 3.5.0 but not 2.9.1).
Actually it would first generate the site locally and validate local.target (on the newly
built site). If the site can validate, it's published and then we verify
unified.target validates against the published site. If local site appears to be missing
IUs, build stops and site is not published.
That way, all TPs published will be fine: Target-platforms published on Nexus are always
in sync and working with the currently published repo. In case of issue (such as the one
we experiment with Lucene core), we end up with having multiple.target on Nexus more
recent than the unified.target.
Deduce all target-platforms (local + unified) from multiple.target
------------------------------------------------------------------
Key: JBIDE-12565
URL:
https://issues.jboss.org/browse/JBIDE-12565
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: Build/Releng, target-platform
Reporter: Mickael Istria
Assignee: Nick Boldt
Fix For: 4.0.0.Alpha2
In order to make maintainance easier and target-platform more reliable, we should improve
the way we create target-platforms so we only maintain multople.target and other platforms
(local, unified) get generated from it.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira