[JBoss JIRA] (JBIDE-21179) Upgrade Forge Runtime to 3.0.0.Alpha2
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21179?page=com.atlassian.jira.plugi... ]
George Gastaldi commented on JBIDE-21179:
-----------------------------------------
As I beforementioned, the impact of this major release is minimal compared to Forge 1 -> Forge 2 (the codebase is the almost the same).
I wanted the JDK 8 upgrade to be a minor release, but the users preferred it to be a major.
> Upgrade Forge Runtime to 3.0.0.Alpha2
> -------------------------------------
>
> Key: JBIDE-21179
> URL: https://issues.jboss.org/browse/JBIDE-21179
> Project: Tools (JBoss Tools)
> Issue Type: Component Upgrade
> Components: forge
> Affects Versions: 4.3.0.Final
> Reporter: George Gastaldi
> Assignee: George Gastaldi
> Labels: new_and_noteworthy
> Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
>
>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBDS-3571) Release note required for JBDS 9.0.1
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBDS-3571?page=com.atlassian.jira.plugin.... ]
Martin Malina commented on JBDS-3571:
-------------------------------------
[~dgolovin], 9.1.0 currently includes internal full build of EAP 6.4.5 which is wrong. I created a JIRA for it here: JBDS-3570 I think it's not clear yet whta 9.1.0.Beta1 installer will include, but it should probably be the same patched EAP 6.4.0.
> Release note required for JBDS 9.0.1
> ------------------------------------
>
> Key: JBDS-3571
> URL: https://issues.jboss.org/browse/JBDS-3571
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Task
> Components: documentation
> Affects Versions: 9.0.1.GA
> Reporter: Len DiMaggio
> Assignee: Supriya Bharadwaj
> Fix For: 9.0.1.GA
>
>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21179) Upgrade Forge Runtime to 3.0.0.Alpha2
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21179?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-21179:
---------------------------------------------
just that JBDS 9.1 is maintanence release and Integration stack uses/pushes forge (especially Fuse) so not sure how this will affect product.
It is really unfortunate that we already have to discuss Forge 2 removal when we removed multiple runtime support (forge 1 vs forge 2) to allow for faster progress assuming Forge 2 would stay more compatible for longer.
> Upgrade Forge Runtime to 3.0.0.Alpha2
> -------------------------------------
>
> Key: JBIDE-21179
> URL: https://issues.jboss.org/browse/JBIDE-21179
> Project: Tools (JBoss Tools)
> Issue Type: Component Upgrade
> Components: forge
> Affects Versions: 4.3.0.Final
> Reporter: George Gastaldi
> Assignee: George Gastaldi
> Labels: new_and_noteworthy
> Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
>
>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBDS-3571) Release note required for JBDS 9.0.1
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3571?page=com.atlassian.jira.plugin.... ]
Denis Golovin edited comment on JBDS-3571 at 12/7/15 9:32 AM:
--------------------------------------------------------------
Do we need to mention inclusion of patched EAP in 9.1.0 installer as well and create separate JIRA for that?
was (Author: dgolovin):
Do we need to mention inclusion of patched EAP in 9.1.0 installer as well?
> Release note required for JBDS 9.0.1
> ------------------------------------
>
> Key: JBDS-3571
> URL: https://issues.jboss.org/browse/JBDS-3571
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Task
> Components: documentation
> Affects Versions: 9.0.1.GA
> Reporter: Len DiMaggio
> Assignee: Supriya Bharadwaj
> Fix For: 9.0.1.GA
>
>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBDS-3571) Release note required for JBDS 9.0.1
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBDS-3571?page=com.atlassian.jira.plugin.... ]
Len DiMaggio commented on JBDS-3571:
------------------------------------
The topic that requires documentation is the upgrade path for JBDS 9.0.0 users.
The possible paths are:
* Install from the new installer - jboss-devstudio-9.0.0.GA-CVE-2015-7501-installer-eap.jar
* Download the EAP release itself
* Apply the EAP pacth to their already installed EAP
> Release note required for JBDS 9.0.1
> ------------------------------------
>
> Key: JBDS-3571
> URL: https://issues.jboss.org/browse/JBDS-3571
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Task
> Components: documentation
> Affects Versions: 9.0.1.GA
> Reporter: Len DiMaggio
> Assignee: Supriya Bharadwaj
> Fix For: 9.0.1.GA
>
>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBDS-3570) Remove EAP 6.4.5 from JBDS installer
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBDS-3570?page=com.atlassian.jira.plugin.... ]
Martin Malina updated JBDS-3570:
--------------------------------
Priority: Critical (was: Major)
> Remove EAP 6.4.5 from JBDS installer
> ------------------------------------
>
> Key: JBDS-3570
> URL: https://issues.jboss.org/browse/JBDS-3570
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Task
> Components: build
> Affects Versions: 9.1.0.Beta1, 10.0.0.Alpha1
> Reporter: Martin Malina
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 9.1.0.Beta1, 10.0.0.Alpha1
>
>
> During the whole thing about JBDS-3560, JBDS-3561 and JBDS-3562, Nick changed JBDS 9.1.0 to use the internal build of EAP 6.4.5 in the build process:
> 4.3.x branch:
> https://github.com/jbdevstudio/jbdevstudio-product/commit/c8aea70202616df...
> And in master:
> https://github.com/jbdevstudio/jbdevstudio-product/commit/6792edbfefcf54d...
> I understand that some of the above mentioned JIRAs are not resolved yet, but I wanted to be sure to track this - we need to make sure not to bundle this build of EAP, because it's an internal build not supposed to be public. (Yes, the original assumption was that perhaps this time there would be an exception, but it turned out not to be the case.)
> For JBDS 9.1.0.Beta1 I suggest we include the same patched EAP as discussed in JBDS-3562 . But it's kind of tricky how to make it obvious to users - I'm not sure if we want to include the CVE in the filename again.
> But in any case, we can never include EAP 6.4.5 full build.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months