[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=13140384#comment-13140384 ] 

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

Since we in the past have found/had several issues including the TP as composite in past I'm curious to grok what this suggestion actually does and if those past issues are not relevant anymore.

a) is this just about the *final* form on the GA site to users ? i.e. Integration stack and other builds would not want the TP included in the composite when depending on this.

b) in past we had TP in associated site to avoid it got listed either in categorized or uncategorized content - is that not an issue anymore ?

c) "we now always co-release JBT with its TP in the same URL" i'm not following as good reason to do this since my assumption is we would be interested in being able to release *smaller* parts rather than bigger parts together ?

sorry if seem like dumb questions but I just remember all the issues that occurred when TP was part of the sites in the past, so just educate me on what changed.

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