[JBoss JIRA] (JBIDE-26071) Add server adapter for WildFly 13
by Mark S (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26071?page=com.atlassian.jira.plugi... ]
Mark S edited comment on JBIDE-26071 at 8/1/18 6:58 PM:
--------------------------------------------------------
I am a bit confused and I am hoping someone can provide a bit of clarity.
Has the server adapter for WildFly 13 been successfully added to the JBoss Tools 4.6.0.Final release? If this server adapter feature has been successfully added, what is this JIRA Issue meant to track (bugs, incomplete solution, features missing)?
*+Background+*
I have been looking forward to the support for Wildfly 13 and when I saw that the fixed version for this JIRA issue updated from 4.6.0.Final to 4.9.0.AM1 ([~nickboldt]) I was surprised, as the planned 4.9.0.Final release date is October 2nd (https://issues.jboss.org/projects/JBIDE?selectedItem=com.atlassian.jira.j...).
However, I just accidentally discovered that I can view the "Wildfly 13" server adapter in my Eclipse Photon instance and then found this feature mentioned in the recent blog post [https://tools.jboss.org/blog/12.0.0.ga-for-photon.html] by [~jeffmaury]
{panel:title= JBoss Tools and Red Hat Developer Studio for Eclipse Photon posted by Jeff Maury on Jul 17, 2018.}
Server tools
Wildfly 13 Server Adapter
A server adapter has been added to work with Wildfly 13. It adds support for Servlet 4.0.
{panel}
was (Author: marks1900):
I am a bit confused and I am hoping someone can provide a bit of clarity.
Has the server adapter for WildFly 13 been successfully added to the JBoss Tools 4.6.0.Final release? If this server adapter feature has been successfully added, what is this JIRA Issue meant to track (bugs, incomplete solution, features missing)?
*+Background+*
I have been looking forward to the support for Wildfly 13 and when I saw that the fixed version for this JIRA issue updated from 4.6.0.Final to 4.9.0.AM1 I was pretty disappointed, as the planned 4.9.0.Final release date is October 2nd (https://issues.jboss.org/projects/JBIDE?selectedItem=com.atlassian.jira.j...).
However, I just accidentally discovered that I can view the "Wildfly 13" server adapter in my Eclipse Photon instance and then found this feature mentioned in the recent blog post [https://tools.jboss.org/blog/12.0.0.ga-for-photon.html] by [~jeffmaury]
{panel:title= JBoss Tools and Red Hat Developer Studio for Eclipse Photon posted by Jeff Maury on Jul 17, 2018.}
Server tools
Wildfly 13 Server Adapter
A server adapter has been added to work with Wildfly 13. It adds support for Servlet 4.0.
{panel}
> Add server adapter for WildFly 13
> ---------------------------------
>
> Key: JBIDE-26071
> URL: https://issues.jboss.org/browse/JBIDE-26071
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server
> Affects Versions: 4.6.0.AM2
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 4.9.0.AM1
>
>
> It turns out WildFly 13 was released yesterday. They're on a quarterly release cadence now apparently. So I wonder how we should deal with this. Perhaps should group some of the versions if there are no breaking changes for us? Or do you think it's better to stick with our current model of always adding a new adapter and that way you can always update the libs?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (JBIDE-26180) TP: create target platform based on Eclipse 4.9 (Simrel 2018-09)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26180?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-26180:
------------------------------------
Changes to Orbit coming in M3:
{quote}com.ibm.icu 56.1.0, 58.2.0 (use 62.0.0)
com.ibm.icu.base 56.1.0, 58.2.0 (use com.ibm.icu 62.0.0)
org.apache.felix.gogo.runtime 1.0.6 (use 1.1.0)
org.apache.felix.gogo.shell 1.0.0 (use 1.1.0)
org.apache.felix.scr 2.0.8, 2.0.10, 2.0.12 (use 2.0.14)
com.google.guava 15.0.0, 18.0.0 (use 21.0.0)
org.apache.ant 1.9.6, 1.10.3 (use 1.10.5, will be in soon){quote}
Possible impacts:
* org.eclipse.recommenders.injection 2.5.3.v20180609-1554 requires com.google.guava 15.0. Unsure if a newer version exists which works w/ Guava 21..
Not sure about the com.ibm.icu stuff -- is 62 compatible with 58?
The rest - the apache felix and ant stuff - should hopefully be fine.
As to Lucene removals:
* org.eclipse.recommenders.models 2.5.3 requires lucene.core 3.5
* o.e.epp.logging.aeri.feature requires lucene.analysis 6.1
* org.eclipse.datatools.sqltools.result (DTP) and org.eclipse.m2e.wtp.jpa.feature (WTP) both require org.apache.lucene.queryparser 6.1.0.v20161115-1612, which doesn't exist in 7.1 (Lucene loves to add and drop bundles will-nilly, don't they?)
So... either those bundles / features need updating to use lucene 7.1+ or else they'll have to build against old Orbit... and Simrel + JBT TP will end up having multiple versions of these IUs peppered in the mix.
> TP: create target platform based on Eclipse 4.9 (Simrel 2018-09)
> ----------------------------------------------------------------
>
> Key: JBIDE-26180
> URL: https://issues.jboss.org/browse/JBIDE-26180
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform, upstream
> Affects Versions: 4.9.0.AM1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.9.0.AM1, 4.9.0.AM2, 4.9.0.AM3, 4.9.0.Final
>
>
> In order to start Eclipse 4.9-based builds, we need an updated target platform.
> For sprint 152 / AM1: simrel M1
> For sprint 153 / AM2: simrel M2
> For sprint 154 / AM3: simrel M3
> For sprint 155 / GA: simrel RC2/GA
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (JBDS-4706) Use "Red Hat Developer Studio" instead of "Red Hat JBoss Developer Studio" in graphics & text
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4706?page=com.atlassian.jira.plugin.... ]
Nick Boldt reassigned JBDS-4706:
--------------------------------
Assignee: Nick Boldt (was: Jeff MAURY)
Resolution: Done
Resolving. Nothing more to do here.
> Use "Red Hat Developer Studio" instead of "Red Hat JBoss Developer Studio" in graphics & text
> ---------------------------------------------------------------------------------------------
>
> Key: JBDS-4706
> URL: https://issues.jboss.org/browse/JBDS-4706
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Task
> Components: build, installer
> Affects Versions: 12.0.0.AM1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 12.0.0.GA
>
> Attachments: DevStudio_iconproduction.zip, JBossPerspective.jpg, about_devstudio.png, devstudio12-central.png, devstudio_banner.png, heading.png, installer01.png, installer02.png, splash.bmp, uninstall.ico
>
>
> Branding has requested that we rename devstudio from "Red Hat JBoss Developer Studio" to "Red Hat Developer Studio".
> We'll need to collect graphics for use in the product and its website on https://devstudio.redhat.com/12/staging/updates/
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (JBDS-4706) Use "Red Hat Developer Studio" instead of "Red Hat JBoss Developer Studio" in graphics & text
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4706?page=com.atlassian.jira.plugin.... ]
Nick Boldt closed JBDS-4706.
----------------------------
> Use "Red Hat Developer Studio" instead of "Red Hat JBoss Developer Studio" in graphics & text
> ---------------------------------------------------------------------------------------------
>
> Key: JBDS-4706
> URL: https://issues.jboss.org/browse/JBDS-4706
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Task
> Components: build, installer
> Affects Versions: 12.0.0.AM1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 12.0.0.GA
>
> Attachments: DevStudio_iconproduction.zip, JBossPerspective.jpg, about_devstudio.png, devstudio12-central.png, devstudio_banner.png, heading.png, installer01.png, installer02.png, splash.bmp, uninstall.ico
>
>
> Branding has requested that we rename devstudio from "Red Hat JBoss Developer Studio" to "Red Hat Developer Studio".
> We'll need to collect graphics for use in the product and its website on https://devstudio.redhat.com/12/staging/updates/
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (JBDS-4706) Use "Red Hat Developer Studio" instead of "Red Hat JBoss Developer Studio" in graphics & text
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4706?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4706:
-----------------------------
Fix Version/s: 12.0.0.GA
(was: 12.9.0.AM1)
> Use "Red Hat Developer Studio" instead of "Red Hat JBoss Developer Studio" in graphics & text
> ---------------------------------------------------------------------------------------------
>
> Key: JBDS-4706
> URL: https://issues.jboss.org/browse/JBDS-4706
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Task
> Components: build, installer
> Affects Versions: 12.0.0.AM1
> Reporter: Nick Boldt
> Assignee: Jeff MAURY
> Priority: Blocker
> Fix For: 12.0.0.GA
>
> Attachments: DevStudio_iconproduction.zip, JBossPerspective.jpg, about_devstudio.png, devstudio12-central.png, devstudio_banner.png, heading.png, installer01.png, installer02.png, splash.bmp, uninstall.ico
>
>
> Branding has requested that we rename devstudio from "Red Hat JBoss Developer Studio" to "Red Hat Developer Studio".
> We'll need to collect graphics for use in the product and its website on https://devstudio.redhat.com/12/staging/updates/
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (JBIDE-26071) Add server adapter for WildFly 13
by Mark S (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26071?page=com.atlassian.jira.plugi... ]
Mark S edited comment on JBIDE-26071 at 8/1/18 2:28 PM:
--------------------------------------------------------
I am a bit confused and I am hoping someone can provide a bit of clarity.
Has the server adapter for WildFly 13 been successfully added to the JBoss Tools 4.6.0.Final release? If this server adapter feature has been successfully added, what is this JIRA Issue meant to track (bugs, incomplete solution, features missing)?
*+Background+*
I have been looking forward to the support for Wildfly 13 and when I saw that the fixed version for this JIRA issue updated from 4.6.0.Final to 4.9.0.AM1 I was pretty disappointed, as the planned 4.9.0.Final release date is October 2nd (https://issues.jboss.org/projects/JBIDE?selectedItem=com.atlassian.jira.j...).
However, I just accidentally discovered that I can view the "Wildfly 13" server adapter in my Eclipse Photon instance and then found this feature mentioned in the recent blog post [https://tools.jboss.org/blog/12.0.0.ga-for-photon.html] by [~jeffmaury]
{panel:title= JBoss Tools and Red Hat Developer Studio for Eclipse Photon posted by Jeff Maury on Jul 17, 2018.}
Server tools
Wildfly 13 Server Adapter
A server adapter has been added to work with Wildfly 13. It adds support for Servlet 4.0.
{panel}
was (Author: marks1900):
I am a bit confused and I am hoping someone can provide a bit of clarity.
Has the server adapter for WildFly 13 been successfully added to the JBoss Tools 4.6.0.Final release? If this server adapter feature has been successfully added, what is this JIRA Issue meant to track (bugs, incomplete solution, features missing)?
*+Background+*
I have been looking forward to the support for Wildfly 13 and when I saw that the fixed version for this JIRA issue updated from 4.6.0.Final to 4.9.0.AM1 I was pretty disappointed, as the planned 4.9.0.Final release date is October 2nd (https://issues.jboss.org/projects/JBIDE?selectedItem=com.atlassian.jira.j...).
However, I just accidentally discovered that I can view the "Wildfly 13" server adapter in my Eclipse Photon instance and then found this feature mentioned in the recent blog post [https://tools.jboss.org/blog/12.0.0.ga-for-photon.html] -
{panel:title= JBoss Tools and Red Hat Developer Studio for Eclipse Photon posted by Jeff Maury on Jul 17, 2018.}
Server tools
Wildfly 13 Server Adapter
A server adapter has been added to work with Wildfly 13. It adds support for Servlet 4.0.
{panel}
> Add server adapter for WildFly 13
> ---------------------------------
>
> Key: JBIDE-26071
> URL: https://issues.jboss.org/browse/JBIDE-26071
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server
> Affects Versions: 4.6.0.AM2
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 4.9.0.AM1
>
>
> It turns out WildFly 13 was released yesterday. They're on a quarterly release cadence now apparently. So I wonder how we should deal with this. Perhaps should group some of the versions if there are no breaking changes for us? Or do you think it's better to stick with our current model of always adding a new adapter and that way you can always update the libs?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months