[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

Mickael Istria (JIRA) issues at jboss.org
Wed Sep 24 10:02:02 EDT 2014


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

Mickael Istria commented on JBIDE-18239:
----------------------------------------

[~nickboldt]:
* I tried them, Tycho validation and mirror mojo support 0.0.0 fine. If for some reason there is a bug I didn't see, then we can fix those mojos
* I believe [~maxandersen] is even in favour of totally removing any org.jboss.tools content from target definition.

[~maxandersen]
* I agree with [~nickboldt] main concern: what about content that is available in JBT aggregate and JBDS central, but not in JBDS main site? Do we want to allow that? If we simply say that such content should always go in JBDS main site, then things are easier. We just need to be sure we're ok with that.

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


More information about the jbosstools-issues mailing list