[JBoss JIRA] (JBTIS-331) Get the integration stack into Early Access in JBoss Central
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBTIS-331?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBTIS-331:
-------------------------------------------
If JBT-IS content need to go on marketplace (and it should) then at least when we have final release it must be available on / otherwise we'll have to keep dragging around needless multiple updatesite urls.
And if we do this I do not see any need to move the pointers around - they will always just be / and when JBT goes final and JBT-IS is not ready then they cannot be in our central as a "fullly supported install" ...then they need to be moved onto earlyaccess updatesite so there are no overlap between released and earlyaccess bits that suddenly shows up in users install when doing Help > Update.
> Get the integration stack into Early Access in JBoss Central
> ------------------------------------------------------------
>
> Key: JBTIS-331
> URL: https://issues.jboss.org/browse/JBTIS-331
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Components: distribution
> Affects Versions: 8.0.0.Alpha2
> Reporter: Paul Leacu
> Assignee: Paul Leacu
>
> Procedure for encorporating the IS into Early Access.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBTIS-331) Get the integration stack into Early Access in JBoss Central
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBTIS-331?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen edited comment on JBTIS-331 at 10/2/14 6:50 AM:
--------------------------------------------------------------------
i.e. if this is just about having IS on jboss tools CR1/Beta's then there is no need to call that earlyaccess.
Then it is just part of the -development package. We can *mark* it as earlyaccess as suggested above but it won't be enough if we want it as earlyaccess on our final/GA central for JBoss Tools and Developer Studio. There it got to move to earlyaccess url site afaics.
Also - I assume we are going to set {jboss.is.update.url} to be http://download.jboss.org/jbosstools/updates/development since thats how it would work ever since https://issues.jboss.org/browse/JBDS-3086 have been made in effect ? (central is now composite into / of the main updatesite)
was (Author: maxandersen):
i.e. if this is just about having IS on jboss tools CR1/Beta's then there is no need to call that earlyaccess.
Then it is just part of the -development package. We can *mark* it as earlyaccess as suggested above but it won't be enough if we want it as earlyaccess on our final/GA central for JBoss Tools and Developer Studio. There it got to move afaics.
> Get the integration stack into Early Access in JBoss Central
> ------------------------------------------------------------
>
> Key: JBTIS-331
> URL: https://issues.jboss.org/browse/JBTIS-331
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Components: distribution
> Affects Versions: 8.0.0.Alpha2
> Reporter: Paul Leacu
> Assignee: Paul Leacu
>
> Procedure for encorporating the IS into Early Access.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18239) Create new update site zip(s) (rather than target platform zip) for JBT content needed for Central/EA site
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18239?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-18239:
---------------------------------------------
Nick, *you* opened the jira. Not I.
And I do repeatedly say *move* the JBoss Tools references in central to the main updatesite so it makes the workflow simpler - no need to bump the versions of that content.
> 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
> Assignee: 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)
11 years, 6 months