[
https://issues.jboss.org/browse/JBIDE-11734?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-11734:
----------------------------------------
Nick, can you please detail the current process to generate sites/TP here, with its
current pitfalls? The main one I see is that we often have unusable target platforms.
Instead I suggest:
# We maintain a site, in the eclipse-repository Tycho way, and manage its content with a
category.xml. This site will include a union of all our requirements for dev and builds
# We also maintain target platforms (a pom with .target files) as we do now. We try to
leverage some validation as suggested in JBIDE-12003 to ensure we can resolve target
platforms from the site
# CI Build job would be:
## Build site
## Publish site to
download.jboss.org
## Validate, Build and publish .target to Nexus
This should really improve usability and maintainability of how we manage and consume
targets. WDYT?
Create TP site using an "eclipse-repository",
<repositories> and category.xml
-----------------------------------------------------------------------------
Key: JBIDE-11734
URL:
https://issues.jboss.org/browse/JBIDE-11734
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: target-platform
Reporter: Mickael Istria
Assignee: Nick Boldt
Fix For: 3.4.0.M1
Instead of parsing and tweaking a .target file to generate the "requirement"
repository, we could make it a normal "eclipse-repository" artifact. We would
manage versions in it.
Then we know the versions of deps in that site, and we can create target platform using
0.0.0 for versions since we are sure they are resolved against our site.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira