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

[Max Rydahl Andersen (JIRA)]

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

Max Rydahl Andersen commented on JBIDE-21233:
---------------------------------------------

a) sorry, but did not follow that answer at all. Did not answer my question on whether  this would be affecting only the final public updatessites or also the internal ones used for builds. If it affects the latter then I don't see how we can build reliably.

b)  You are now showing me something that should *not* happen. This TP should not be listed in the list of available updatesites. That is a bug and something that should never have happened. This is why we moved to use the p2 associate sites(not sure if right term) since it avoided it to be shown in here, and we didn't use composite sites in the past since it caused problems with content showing up in uncategorized. Is that fixed ?  Are you saying that at some point we moved back from the lower level p2 concept (that does not show up in p2 update ui) to use associate sites and this jira is about undoing that mistake ? 
 
c) If you refute this statement then I don't know what to say. That is and has been a goal for years to avoid building larger and larger releases. 



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