[jbosstools-issues] [JBoss JIRA] (JBIDE-11734) Create TP site using an "eclipse-repository", <repositories> and category.xml

[Mickael Istria (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-11734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12705675#comment-12705675 ] 

Mickael Istria commented on JBIDE-11734:
----------------------------------------

{quote}
which would be category.xml
Which you'd have to generate in order to keep in sync w/ the .target file, or else would result in duplication of effort/maintenance.
{quote}
Seems like the current synchronization mechanism is often failing to provide usable target platforms. I think an approach based on 1 autonomous site + target platforms to select subsets of this site would be more maintainable.

{quote}
What about https://svn.jboss.org/repos/jbosstools/trunk/build/target-platform/unified.target ? Is that not a single entry point? 
{quote}
Nope. Entry points are:
* Updates/requirements site to mirror
* Composite*.xml files to select requirements sites on which target-platform resolution will occur
* multiple.target to get a target on the composite site, and to generate an aggregation script from
* unified.target as the final artifact.

The flow makes that we go from target platform to a site through a script and then we build a target platform on top of the site.
I'm thinking we could get rid of the multiple in favor of a category.xml and make unified pull its stuff from it.

Of course, when adding a new IU, process would be to add it to category.xml, build and publish site, and then validate and publish unified. Currently, it's the same, except that we modify multiple.target instead of a category file, and that we rely on composite to list sites rather than a pom.xml.
We move to more standard approaches, with easier maintenance.

On a side note: https://bugs.eclipse.org/bugs/show_bug.cgi?id=383865
                
> 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: Mickael Istria
>             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