[jbosstools-issues] [JBoss JIRA] (JBIDE-21233) remove need for a targetplatforms/jbosstoolstarget/neon site

[Nick Boldt (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-21233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nick Boldt updated JBIDE-21233:
-------------------------------
    Attachment: jbt-creeping-update-sites.png


a) This replaces the "lastest max TP" composites, eg.,

http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/kepler/compositeArtifacts.xml (4.32.0.Final)
http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/luna/compositeArtifacts.xml (4.42.0.Final)
http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/mars/compositeArtifacts.xml (currently 4.51.0.Final, but will move to 4.52.0.Final in March)

For our kepler we did this:

http://download.jboss.org/jbosstools/updates/stable/kepler/compositeContent.xml -> http://download.jboss.org/jbosstools/static/releases/JBossTools-4.1.2.Final.core/

There is TP in the composite; so, to resolve deps, the TP is only available from the update site's metadata via associate site. Therefore the "vanity" URL http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/kepler/ is needed.

Then for Luna, we added the JBT TP (and the Central bits too) into the composite:

http://download.jboss.org/jbosstools/updates/stable/luna/compositeContent.xml -> {code}
<child location="http://download.jboss.org/jbosstools/static/releases/jbosstools-4.2.3.Final-updatesite-core/"/>
<child location="http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.42.0.Final/REPO/"/>
<child location="http://download.jboss.org/jbosstools/static/targetplatforms/jbtcentraltarget/4.42.0.Final/REPO/"/>
<child location="http://download.jboss.org/jbosstools/updates/stable/luna/integration-stack/"/>{code}

Now, we no longer need the vanity URL, but we STILL link to it in the update site's metadata via associate site. Therefore this vanity URL is redundant.

And now, for Mars, we continue to add the JBT TP (and Central bits + their TP) to the composite:

http://download.jboss.org/jbosstools/updates/stable/mars/compositeContent.xml -> {code}
<child location="http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.51.0.Final/REPO/"/>
<child location="http://download.jboss.org/jbosstools/static/mars/stable/updates/core/4.3.0.Final/"/>
<child location="http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/4.50.0.Final-SNAPSHOT/REPO/"/>
<child location="http://download.jboss.org/jbosstools/static/mars/stable/updates/central/4.3.0.Final/"/>
<child location="http://download.jboss.org/jbosstools/mars/stable/updates/integration-stack/"/>{code}

So, as with Luna, we no longer need the vanity URL, but we STILL link to it in the update site's metadata via associate site. Therefore this vanity URL is redundant.

Thus, we should be able to safely remove it from 4.3.1 and 4.4.0, since we don't need it anymore.

b) 

1. unpack Eclipse Mars.1 JEE 
2. Help > Install > http://download.jboss.org/jbosstools/updates/stable/mars/ > install Central Community feature > cold restart (shut down, start up again).
3. Preferences > Install/Update > Available Software Sites > [^jbt-creeping-update-sites.png]

So, the vanity URL TP site creeps into the list of avail sites (along with the IS site and its TP too). To me this says we don't need to include it as an associate site AND have it appear in the list of available sites. 

> remove need for a targetplatforms/jbosstoolstarget/neon site
> ------------------------------------------------------------
>
>                 Key: JBIDE-21233
>                 URL: https://issues.jboss.org/browse/JBIDE-21233
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: build, target-platform
>    Affects Versions: 4.4.0.Alpha1
>            Reporter: Nick Boldt
>            Assignee: Nick Boldt
>             Fix For: 4.4.0.Alpha1
>
>         Attachments: jbt-creeping-update-sites.png
>
>
> For the last few years, we've had an associate site ref inside the JBT agg site, pointing at "the latest maximum TP", eg., http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/mars/
> But since we now always co-release JBT with its TP in the same URL, this is only useful for someone who wants to do an OFFLINE install using the zip, which will then go ONLINE to resolve TP dependencies. It's at best a broken use case, and at worst it's unnecessary cruft to maintain. 
> Therefore I propose we stop linking to this site.
> We can build the aggregates using a specific TP (the one in the parent pom, natch), and simply NOT use an associate site in the JBT aggregate site build.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)