[jbosstools-issues] [JBoss JIRA] (JBIDE-18239) Create new update site zip(s) (rather than target platform zip) for JBT content needed for Central/EA site

[Nick Boldt (JIRA)]

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

Nick Boldt updated JBIDE-18239:
-------------------------------
    Attachment: JBIDE18239-proposed.png


Re-read Max's comments above and now I'm even more confused what he wants:

{quote}
1. TP containing only 3rd party pieces that do not move often
2. Update site containing what is in #1
{quote}

We already have an update site containing what is in the Central TP. Every TP is built as an update site. In this case, the latest is here: 

http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/4.40.0.CR2-SNAPSHOT/REPO/

{quote}
 i'm suggesting the creation of the update site(s) could be done so we do not need to list the exact versions of JBoss Tools provided content.
{quote}

So in other words you want a TP we can validate which includes 0.0.0, as Mickael suggested. Can't recall if Tycho supports validation of TPs with 0.0.0 in them. Pretty sure the validator chokes on that, or we would have that in place for JBTIS.

Or you want a Central TP site + a second update site built from category.xml (which includes NO versions at all, not even 0.0.0), and that these two be composited together. This IMHO is the best solution as it fully compartmentalizes the stuff in JBDS Central which comes from JBT. 

Alternatively, we could have a JBT Central .target and a JBDS Central .target, but that's even more on-disk footprint and more .target files to maintain and publish to Nexus. 

{quote}i'm suggesting we make it part of the jbds site.{quote}

That's a completely different suggestion -- if I read you correctly (and I'm probably not) then you're NOW asking that the JBT content currently in Central TP which is NOT part of JBDS be added to the JBDS update site so that it's available to Central, and removed from the Central TP. Sure, we can do that ... but it will mean the JBT content that SHOULD be located in the Central update site zip (for offline users) will instead be part of the JBDS update site zip. 

Won't that cause confusion / imply a different level of support than GSS intends?

----

Long story short (TL;DR): I think we need a new category.xml for the stuff that's NOT in JBDS. Here's a visual representation of this new site:

!JBIDE18239-proposed.png!


> Create new update site zip(s) (rather than target platform zip) for JBT content needed for Central/EA site
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-18239
>                 URL: https://issues.jboss.org/browse/JBIDE-18239
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: build, central, discovery, updatesite
>    Affects Versions: 4.2.0.CR1
>            Reporter: Nick Boldt
>              Labels: f2f2014
>             Fix For: 4.3.0.Alpha1
>
>         Attachments: JBIDE18239-proposed.png
>
>
> In order to simplify the process for getting JBT features into Central (for JBDS) and EA (for both JBT/JBDS), it's been suggested (by [~maxandersen], who doesn't like opening JIRAs :D) that instead of a target platform which needs to be updated every time we spin or respin a build, we could instead just produce an update site containing the handful of IUs (cordovasim, arquillian, etc.).
> We could further extend this idea to include all the things that currently are in BOTH JBT or JBDS and in Central, such as TestNG.
> These would be produced as new zips using the JBT aggregate builder:
> https://github.com/jbosstools/jbosstools-build-sites/tree/master/aggregate/
> Need to decide what to call this... "Extras" "JBT-not-in-JBDS" "Shared" ...?



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)