[JBoss JIRA] (JBIDE-26157) Support for JEE8 projects
by Dawid Olejnik (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26157?page=com.atlassian.jira.plugi... ]
Dawid Olejnik commented on JBIDE-26157:
---------------------------------------
Also, neither ears built as J2EE 8 work.
!screenshot-2.png|thumbnail!
> Support for JEE8 projects
> -------------------------
>
> Key: JBIDE-26157
> URL: https://issues.jboss.org/browse/JBIDE-26157
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: common, server
> Reporter: Dawid Olejnik
> Assignee: Jeff MAURY
> Fix For: 4.9.x
>
> Attachments: screenshot-1.png, screenshot-2.png
>
>
> Need support for EARs version 8 and WARs with servlets 4.0
> Steps to reproduce:
> * create a dynamic web project and set servlet facet version to 4.0
> * create a Wildfly 13 or 12 instance
> * try to add the project to the server and you will get the dialog
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-26157) Support for JEE8 projects
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26157?page=com.atlassian.jira.plugi... ]
Jeff MAURY reassigned JBIDE-26157:
----------------------------------
Assignee: Jeff MAURY (was: Rob Stryker)
> Support for JEE8 projects
> -------------------------
>
> Key: JBIDE-26157
> URL: https://issues.jboss.org/browse/JBIDE-26157
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: common, server
> Reporter: Dawid Olejnik
> Assignee: Jeff MAURY
> Fix For: 4.9.x
>
> Attachments: screenshot-1.png
>
>
> Need support for EARs version 8 and WARs with servlets 4.0
> Steps to reproduce:
> * create a dynamic web project and set servlet facet version to 4.0
> * create a Wildfly 13 or 12 instance
> * try to add the project to the server and you will get the dialog
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-26157) Support for JEE8 projects
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26157?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-26157:
-------------------------------
Description:
Need support for EARs version 8 and WARs with servlets 4.0
Steps to reproduce:
* create a dynamic web project and set servlet facet version to 4.0
* create a Wildfly 13 or 12 instance
* try to add the project to the server and you will get the dialog
was:Need support for EARs version 8 and WARs with servlets 4.0
> Support for JEE8 projects
> -------------------------
>
> Key: JBIDE-26157
> URL: https://issues.jboss.org/browse/JBIDE-26157
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: common, server
> Reporter: Dawid Olejnik
> Assignee: Jeff MAURY
> Fix For: 4.9.x
>
> Attachments: screenshot-1.png
>
>
> Need support for EARs version 8 and WARs with servlets 4.0
> Steps to reproduce:
> * create a dynamic web project and set servlet facet version to 4.0
> * create a Wildfly 13 or 12 instance
> * try to add the project to the server and you will get the dialog
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-26157) Support for JEE8 projects
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26157?page=com.atlassian.jira.plugi... ]
Jeff MAURY reassigned JBIDE-26157:
----------------------------------
Assignee: Rob Stryker (was: Jeff MAURY)
> Support for JEE8 projects
> -------------------------
>
> Key: JBIDE-26157
> URL: https://issues.jboss.org/browse/JBIDE-26157
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: common, server
> Reporter: Dawid Olejnik
> Assignee: Rob Stryker
> Fix For: 4.9.x
>
> Attachments: screenshot-1.png
>
>
> Need support for EARs version 8 and WARs with servlets 4.0
> Steps to reproduce:
> * create a dynamic web project and set servlet facet version to 4.0
> * create a Wildfly 13 or 12 instance
> * try to add the project to the server and you will get the dialog
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-26170) Define JAVAxx and OPENJDKxx for new JDKs and OpenJDKs installed
by Jeff MAURY (JIRA)
Jeff MAURY created JBIDE-26170:
----------------------------------
Summary: Define JAVAxx and OPENJDKxx for new JDKs and OpenJDKs installed
Key: JBIDE-26170
URL: https://issues.jboss.org/browse/JBIDE-26170
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: build
Affects Versions: 4.6.0.Final
Reporter: Jeff MAURY
Assignee: Martin Malina
Fix For: 4.9.0.AM1
The JBoss Tools JDK9+ jobs rely on JAVAxx and OPENJDKxx variables through the toolchains.xml file. As we want to move those jobs to Java10 and Java11, we need those variables to be defined
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-25000) Server adapter: starting into debugging fails initially (succeeds on a latter try)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25000?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-25000:
------------------------------------------
Another worthwile idea is to increase the timeout when connecting. The current implementation in org.eclipse.wst.jsdt.chromium is using a hardcoded timeout of 3 seconds though:
{code:title=org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl}
...
private static final int WAIT_FOR_HANDSHAKE_TIMEOUT_MS = 3000;
...
try {
remoteInfo = handshaker.getRemoteInfo().get(WAIT_FOR_HANDSHAKE_TIMEOUT_MS,
TimeUnit.MILLISECONDS);
} catch (InterruptedException e) {
throw new RuntimeException(e);
} catch (ExecutionException e) {
throw newIOException("Failed to get version", e);
{code}
> Server adapter: starting into debugging fails initially (succeeds on a latter try)
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-25000
> URL: https://issues.jboss.org/browse/JBIDE-25000
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.0.AM2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: openshift_v3, server_adapter
> Fix For: 4.6.0.Final
>
> Attachments: failed-to-connect-v8-vm.png
>
>
> # ASSERT: have an application running in *[OpenShift Online|https://console.starter-us-east-2.openshift.com/]* based on the "nodejs-mongo-persistent" template
> # ASSERT: have a server adapter for it
> # EXEC/ASSERT: have the adapter started in non-debugging/normal mode
> # EXEC: restart the adapter debugging
> Result:
> !failed-to-connect-v8-vm.png!
> {code}
> java.io.IOException: Failed to get version
> at org.eclipse.wst.jsdt.chromium.internal.v8native.JavascriptVmImpl.newIOException(JavascriptVmImpl.java:114)
> at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:132)
> at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attach(StandaloneVmImpl.java:79)
> at org.eclipse.wst.jsdt.chromium.debug.core.model.JavascriptVmEmbedderFactory$4$1.attach(JavascriptVmEmbedderFactory.java:207)
> at org.eclipse.wst.jsdt.chromium.debug.core.model.DebugTargetImpl.attach(DebugTargetImpl.java:74)
> at org.eclipse.wst.jsdt.chromium.debug.ui.launcher.LaunchTypeBase.launch(LaunchTypeBase.java:101)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039)
> at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> Caused by: java.util.concurrent.ExecutionException: java.io.IOException: End of stream
> at java.util.concurrent.FutureTask.report(FutureTask.java:122)
> at java.util.concurrent.FutureTask.get(FutureTask.java:206)
> at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:127)
> ... 9 more
> Caused by: java.io.IOException: End of stream
> at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl$HandshakeTaks.call(Handshaker.java:127)
> at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl$HandshakeTaks.call(Handshaker.java:1)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl.perform(Handshaker.java:104)
> at org.eclipse.wst.jsdt.chromium.internal.transport.SocketConnection$ReaderThread.run(SocketConnection.java:158)
> {code}
> ps. this can be simulated in the CDK, by having everything set and once the pod is up and ithe adapter is in debug, stopping the port forwarding.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months