[JBoss JIRA] (JBIDE-26390) WildFly 14 does not allow JEE 8 deployments
by Emond Papegaaij (JIRA)
Emond Papegaaij created JBIDE-26390:
---------------------------------------
Summary: WildFly 14 does not allow JEE 8 deployments
Key: JBIDE-26390
URL: https://issues.jboss.org/browse/JBIDE-26390
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Affects Versions: 4.9.0.AM3
Environment: WildFly 14.0.1.Final
Reporter: Emond Papegaaij
Attachments: image-2018-10-01-11-32-34-038.png
When trying to deploy an ear with version 8, you get the following error: The server does not support version 8.0 of the J2EE Enterprise application specification. (see screenshot)
It seems the updated specs were not added to the metadata for WildFly 14.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 3 months
- 1
- 0
[JBoss JIRA] (JBIDE-26312) Windows 7 slaves stall for 7 hours while recording test results?
by Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26312?page=com.atlassian.jira.plugi... ]
Josef Kopriva updated JBIDE-26312:
----------------------------------
Fix Version/s: 4.x
(was: 4.9.0.Final)
> Windows 7 slaves stall for 7 hours while recording test results?
> ----------------------------------------------------------------
>
> Key: JBIDE-26312
> URL: https://issues.jboss.org/browse/JBIDE-26312
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.9.0.AM3
> Reporter: Nick Boldt
> Assignee: Josef Kopriva
> Fix For: 4.x
>
>
> This has been happening for a while now.
> {code}
> 20:24:20 Archiving artifacts
> 20:50:34 Recording test results
> (nothing happens for like 7 hours)
> 04:09:55 Agent went offline during the build
> 04:09:55 ERROR: Connection was broken: java.nio.channels.ClosedChannelException
> 04:09:55 at org.jenkinsci.remoting.protocol.NetworkLayer.onRecvClosed(NetworkLayer.java:154)
> 04:09:55 at org.jenkinsci.remoting.protocol.impl.NIONetworkLayer.ready(NIONetworkLayer.java:179)
> 04:09:55 at org.jenkinsci.remoting.protocol.IOHub$OnReady.run(IOHub.java:721)
> 04:09:55 at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
> 04:09:55 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> 04:09:55 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> 04:09:55 at java.lang.Thread.run(Thread.java:748)
> {code}
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/server.i...
> Anyone have a clue why collecting junit results should take >7hrs on win7, but work fine on other OSes?
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/server.i...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 3 months
- 1
- 0
[JBoss JIRA] (JBIDE-26375) Investigate OpenShift ITests job failures
by Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26375?page=com.atlassian.jira.plugi... ]
Josef Kopriva updated JBIDE-26375:
----------------------------------
Fix Version/s: 4.x
(was: 4.9.0.Final)
> Investigate OpenShift ITests job failures
> -----------------------------------------
>
> Key: JBIDE-26375
> URL: https://issues.jboss.org/browse/JBIDE-26375
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: integration-tests, openshift
> Affects Versions: 4.9.0.Final
> Environment: CentralCI
> Reporter: Josef Kopriva
> Assignee: Josef Kopriva
> Priority: Critical
> Fix For: 4.x
>
>
> Job is failing in last week.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 3 months
- 1
- 0