[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:comment-tabpanel&focusedCommentId=13143003#comment-13143003 ] 

Nick Boldt commented on JBIDE-21233:
------------------------------------

Occurs to me the only reason to KEEP this targetplatforms/jbosstoolstarget/neon URL is so that old JBT releases (4.3.0) can automatically link to the LATEST TP (4.52.x) rather than the one against which it was built. 

But since an existing JBT user will have http://download.jboss.org/jbosstools/mars/stable/updates/ in their Eclipse, which will be updated to point at BOTH a newer JBT (4.3.1) and a newer TP (4.52.x), we achieve the same thing.

Note too that there's no JBDS equivalent targetplatforms/jbdevstudiotarget/neon URL because (for the same reason) we don't need it. We just update https://devstudio.redhat.com/9.0/stable/updates/ with the latest JBDS and TP, and bob's your uncle, all is well -- latest updates delivered and no new clutter in Available Software Sites.

Bottom line: we're doing something different for JBT than for JBDS, and the net is more maintenance and more Available Software Sites clutter. Surely we should follow the path of "less work, cleaner list of Avail Software Sites" that we use for JBDS when building JBT, too?

Have I missed a reason for keeping this extra URL that provides some value we're not achieving some other way?

> 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)