[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

[Max Rydahl Andersen (JIRA)]

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

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

It is clearly neither i'm suggesting. See my first comment:

"The idea was that we don't need the entries for jboss tools based plugins in the actual central TP."

That means that the content coming from JBT is *NOT* to be in central TP but into the main JBDS TP (the one used for creating the main updatesite).

A talks about *all* JBT and putting in central - so that is not it.
B talks about an additional updatesite - that is not what i'm suggesting either.

And no, early access and central updatesites CANNOT be in the same updatesite - that have been discussed ad libitum before how that is not okey since:

A) Earlyaccess IS NOT central

B) if you add earlyaccess into central then users running Help > Check for updates (or install) will get earlyaccess content even though they have not enabled it.

I would really appreciate if we stop having to return to that item again - central IS NOT earlyaccess and vice versa thus they cannot be intermingled.
 
i suggest we park this and go through this during f2f or at least after CR2 since now is really not the time to such revamps that needs testing.


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