[JBoss JIRA] (JBIDE-26071) Add server adapter for WildFly 13
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26071?page=com.atlassian.jira.plugi... ]
Pavol Srna updated JBIDE-26071:
-------------------------------
Priority: Blocker (was: Major)
> 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.6.0.Final
>
>
> 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, 9 months
[JBoss JIRA] (JBIDE-26071) Add server adapter for WildFly 13
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26071?page=com.atlassian.jira.plugi... ]
Pavol Srna updated JBIDE-26071:
-------------------------------
Fix Version/s: 4.6.0.Final
> 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
> Fix For: 4.6.0.Final
>
>
> 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, 9 months
[JBoss JIRA] (JBIDE-25597) TP: create target platforms based on Eclipse Photon
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25597?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-25597 at 6/13/18 12:02 AM:
--------------------------------------------------------------
Updates for AM3:
cameltooling;1.0.0.201806081234
docker;4.0.0.201806120452 (from updates-docker-nightly-photon)
orbit;R20180606145124
photon;201806121200-Photon.0.RC3; (from /staging/photon)
reddeer;2.2.0.RC1-v20180601-0713
tm;3.7.100_4.4.0.20180611 (from new composite http://download.eclipse.org/tm/repository/photon )
webtools;S-3.10.0.RC4-20180611164516
Orbit bundles added/removed:
{code}
+ <unit id="javax.xml.soap" version="1.2.0.v201005080501"/>
+ <unit id="javax.mail" version="1.4.0.v201005080615"/>
+ <unit id="org.apache.commons.discovery" version="0.2.0.v201004190315"/>
+ <unit id="org.apache.commons.httpclient" version="3.1.0.v201012070820"/>
+ <unit id="org.apache.wsil4j" version="1.0.0.v20180522-1857"/>
+ <unit id="org.uddi4j" version="2.0.5.v200805270300"/>
- <unit id="org.apache.commons.collections" version="3.2.2.v201511171945"/>
{code}
WTP feature removed:
{code}- <unit id="org.eclipse.wst.ws_wsdl15.feature.feature.group" version="1.5.400.v201801251811"/>
{code}
Now, we have the following IUs with multiple versions:
{code}
[WARNING] Found 11 duplicate jbosstools plugins:
[WARNING] [1] jbosstools-multiple.target.repo/plugins/com.google.guava_21.0.0.v20170206-1425.jar
[WARNING] [1] jbosstools-multiple.target.repo/plugins/com.google.guava_15.0.0.v201403281430.jar
[WARNING] [2] jbosstools-multiple.target.repo/plugins/org.apache.batik.css_1.9.1.v20180313-1559.jar
[WARNING] [2] jbosstools-multiple.target.repo/plugins/org.apache.batik.css_1.7.0.v201011041433.jar
[WARNING] [3] jbosstools-multiple.target.repo/plugins/org.apache.batik.util_1.7.0.v201011041433.jar
[WARNING] [3] jbosstools-multiple.target.repo/plugins/org.apache.batik.util_1.9.1.v20180227-1645.jar
[WARNING] [4] jbosstools-multiple.target.repo/plugins/org.apache.commons.codec_1.10.0.v20180409-1845.jar
[WARNING] [4] jbosstools-multiple.target.repo/plugins/org.apache.commons.codec_1.9.0.v20170208-1614.jar
[WARNING] [5] jbosstools-multiple.target.repo/plugins/org.apache.commons.logging_1.2.0.v20180409-1502.jar
[WARNING] [5] jbosstools-multiple.target.repo/plugins/org.apache.commons.logging_1.1.1.v201101211721.jar
[WARNING] [6] jbosstools-multiple.target.repo/plugins/org.apache.lucene.analyzers-common_7.1.0.v20180122-2126.jar
[WARNING] [6] jbosstools-multiple.target.repo/plugins/org.apache.lucene.analyzers-common_6.1.0.v20161115-1612.jar
[WARNING] [7] jbosstools-multiple.target.repo/plugins/org.apache.lucene.core_6.1.0.v20170814-1820.jar
[WARNING] [7] jbosstools-multiple.target.repo/plugins/org.apache.lucene.core_3.5.0.v20120725-1805.jar
[WARNING] [7] jbosstools-multiple.target.repo/plugins/org.apache.lucene.core_7.1.0.v20171214-1510.jar
[WARNING] [8] jbosstools-multiple.target.repo/plugins/org.eclipse.jdt.annotation_1.1.200.v20171205-1334.jar
[WARNING] [8] jbosstools-multiple.target.repo/plugins/org.eclipse.jdt.annotation_2.2.0.v20180417-0931.jar
[WARNING] [9] jbosstools-multiple.target.repo/plugins/org.objectweb.asm_6.1.1.v20180414-0329.jar
[WARNING] [9] jbosstools-multiple.target.repo/plugins/org.objectweb.asm_5.0.1.v201404251740.jar
[WARNING] [10] jbosstools-multiple.target.repo/plugins/org.slf4j.api_1.7.2.v20121108-1250.jar
[WARNING] [10] jbosstools-multiple.target.repo/plugins/org.slf4j.api_1.7.10.v20170428-1633.jar
[WARNING] [11] jbosstools-multiple.target.repo/plugins/org.w3c.dom.smil_1.0.1.v200903091627.jar
[WARNING] [11] jbosstools-multiple.target.repo/plugins/org.w3c.dom.smil_1.0.0.v200806040011.jar
{code}
was (Author: nickboldt):
Updates for AM3:
cameltooling;1.0.0.201806081234
docker;4.0.0.201806120452 (from updates-docker-nightly-photon)
orbit;R20180606145124
photon;201806121200-Photon.0.RC3; (from /staging/photon)
reddeer;2.2.0.RC1-v20180601-0713
tm;3.7.100_4.4.0.20180611 (from new composite http://download.eclipse.org/tm/repository/photon )
webtools;S-3.10.0.RC4-20180611164516
> TP: create target platforms based on Eclipse Photon
> ---------------------------------------------------
>
> Key: JBIDE-25597
> URL: https://issues.jboss.org/browse/JBIDE-25597
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: target-platform
> Affects Versions: 4.5.2.Final
> Reporter: Jeff MAURY
> Assignee: Nick Boldt
> Labels: target-platform
> Fix For: 4.6.0.AM3, 4.6.0.Final
>
> Attachments: base.log
>
>
> In order to start Photon based builds, we need a working Photon based target platform
> For sprint 148 / AM1: Photon.0.M6
> For sprint 149 / AM2: Photon.0.M7
> For sprint 150 / AM3: Photon.0.RC3
> For sprint 151 / GA: Photon.0.GA
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-25597) TP: create target platforms based on Eclipse Photon
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25597?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-25597:
------------------------------------
Updates for AM3:
cameltooling;1.0.0.201806081234
docker;4.0.0.201806120452 (from updates-docker-nightly-photon)
orbit;R20180606145124
photon;201806121200-Photon.0.RC3; (from /staging/photon)
reddeer;2.2.0.RC1-v20180601-0713
tm;3.7.100_4.4.0.20180611 (from new composite http://download.eclipse.org/tm/repository/photon )
webtools;S-3.10.0.RC4-20180611164516
> TP: create target platforms based on Eclipse Photon
> ---------------------------------------------------
>
> Key: JBIDE-25597
> URL: https://issues.jboss.org/browse/JBIDE-25597
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: target-platform
> Affects Versions: 4.5.2.Final
> Reporter: Jeff MAURY
> Assignee: Nick Boldt
> Labels: target-platform
> Fix For: 4.6.0.AM3, 4.6.0.Final
>
> Attachments: base.log
>
>
> In order to start Photon based builds, we need a working Photon based target platform
> For sprint 148 / AM1: Photon.0.M6
> For sprint 149 / AM2: Photon.0.M7
> For sprint 150 / AM3: Photon.0.RC3
> For sprint 151 / GA: Photon.0.GA
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-26094) Debugging support: Basic Implementation
by Rob Stryker (JIRA)
Rob Stryker created JBIDE-26094:
-----------------------------------
Summary: Debugging support: Basic Implementation
Key: JBIDE-26094
URL: https://issues.jboss.org/browse/JBIDE-26094
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: stack-server-protocol
Affects Versions: 4.6.0.AM2
Reporter: Rob Stryker
Allow for basic support for debugging. The two usecases which should be covered are:
1) server/getLaunchCommand
2) server/startServerAsync
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-26093) Debugging Support
by Rob Stryker (JIRA)
Rob Stryker created JBIDE-26093:
-----------------------------------
Summary: Debugging Support
Key: JBIDE-26093
URL: https://issues.jboss.org/browse/JBIDE-26093
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: stack-server-protocol
Affects Versions: 4.6.0.AM2
Reporter: Rob Stryker
SSP clients needs to be able to either have the SSP launch a given server in debug mode, or, ask the SSP for a launch command with debug flags applied.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months