]
Nick Boldt commented on JBIDE-21233:
------------------------------------
c) I refute your assumption, "my assumption is we would be interested in being able
to release smaller parts rather than bigger parts together". When? How? Why?
Schedule? Plan? JIRA?
Besides, if we release pieces of JBT independent of the whole aggregate, they can be
composited into a single site AND that composite can also include a child site link to the
shared TP. So there's still no need for an associate site.
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.