[
https://issues.jboss.org/browse/JBIDE-11734?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-11734:
----------------------------------------
Nick said:
{quote}
individual requirement mirror defines which features we want to mirror, eg.,
http://download.jboss.org/jbosstools/updates/requirements/mylyn/build.xml
then the composite site defines which versions of the requirement we want to collect
it's like having a category.xml to list the IUs, but it keeps the mapping between
[requirement type]::-[list of features] and [version of the collection]::-[requirement
type] in two places
first a build.xml (or pom.xml if you prefer) to define the requirement mirror itself
then a composite*.xml pair to define which mirrors are needed in the overall reqs site
and then your .target file can be the filter
{quote}
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