[JBoss JIRA] (JBIDE-26156) "forein key name ([name]) mapped to different tables!" reading schema to import the entities from db tables.
by Matt B (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26156?page=com.atlassian.jira.plugi... ]
Matt B commented on JBIDE-26156:
--------------------------------
CREATE TABLE "dbm"."TableA" (
"Id" INTEGER NOT NULL,
"Name" CHAR(20) NULL,
PRIMARY KEY ( "Id" ASC )
) IN "system";
CREATE TABLE "dbm"."TableB" (
"Id" INTEGER NOT NULL,
"name" CHAR(20) NULL,
"tableA" INTEGER NULL,
PRIMARY KEY ( "Id" ASC )
) IN "system";
CREATE TABLE "dbm"."TableC" (
"Id" INTEGER NOT NULL,
"name" CHAR(20) NULL,
"tableA" INTEGER NULL,
PRIMARY KEY ( "Id" ASC )
) IN "system";
ALTER TABLE "dbm"."TableB" ADD CONSTRAINT "TableA" FOREIGN KEY ( "tableA" ASC ) REFERENCES "dbm"."TableA" ( "Id" ) ON UPDATE CASCADE;
ALTER TABLE "dbm"."TableC" ADD CONSTRAINT "TableA" FOREIGN KEY ( "tableA" ASC ) REFERENCES "dbm"."TableA" ( "Id" ) ON UPDATE CASCADE;
> "forein key name ([name]) mapped to different tables!" reading schema to import the entities from db tables.
> ------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-26156
> URL: https://issues.jboss.org/browse/JBIDE-26156
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.5.3.Final
> Environment: Windows 8.1
> Eclipse version: Oxygen.3a Release (4.7.3a)
> Jboss Tools 4.5.3.Final
> SAP Sql Anywhere v.17.0.8.4103
> Reporter: Matt B
> Assignee: Koen Aers
> Priority: Critical
>
> Default name of sql anywhere's foreign key is the name of the destination table.
> If more tables link to same table, can be present di default more foreign key with same name.
> importing the entities from db tables do the error in subject
> Please manage this case.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-26156) "forein key name ([name]) mapped to different tables!" reading schema to import the entities from db tables.
by Matt B (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26156?page=com.atlassian.jira.plugi... ]
Matt B updated JBIDE-26156:
---------------------------
Steps to Reproduce:
TableB -> TableA with foreign key name TableA
TableC -> TableA with foreign key name TableA
Import the entities from db tables.
the hibernate tool, reading the scherma, do error in subject
was:
Table A -> Table B with foreign key name name1
Table C -> Table B with foreign key name name1
Import the entities from db tables.
the hibernate tool, reading the scherma, do error in subject
> "forein key name ([name]) mapped to different tables!" reading schema to import the entities from db tables.
> ------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-26156
> URL: https://issues.jboss.org/browse/JBIDE-26156
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.5.3.Final
> Environment: Windows 8.1
> Eclipse version: Oxygen.3a Release (4.7.3a)
> Jboss Tools 4.5.3.Final
> SAP Sql Anywhere v.17.0.8.4103
> Reporter: Matt B
> Assignee: Koen Aers
> Priority: Critical
>
> Default name of sql anywhere's foreign key is the name of the destination table.
> If more tables link to same table, can be present di default more foreign key with same name.
> importing the entities from db tables do the error in subject
> Please manage this case.
--
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 edited comment on JBIDE-25000 at 7/3/18 8:55 AM:
------------------------------------------------------------------
I tried 2 approaches, but both didn't work:
* catch the connection error and try again:
doesn't work, the error occurrs in a different thread
* connect beforehand via a dummy socket to see if the port is ready:
doesn't work, port forwarding lets you always connect but this wont tell you if the end of the pipe is ready.
It looks to me as if the only way to achieve this is to make sure that there's a readyness probe for the debug-port, too?
[~jeffmaury] Thoughts?
was (Author: adietish):
I tried 2 approaches, but both didn't work:
* catch the connection error and try again:
doesn't work, the error occurrs in a different thread
* connect beforehand via a dummy socket to see if the port is ready:
doesn't work, port forwarding lets you always connect but this wont tell you if the end of the pipe is ready.
It looks to me as if the only way to achieve this is to make sure that there's a readyness probe for the debug-port, too?
[~jeffmaury] Thoughts?
> 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
[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 edited comment on JBIDE-25000 at 7/3/18 8:54 AM:
------------------------------------------------------------------
I tried 2 approaches, but both didn't work:
* catch the connection error and try again:
doesn't work, the error occurrs in a different thread
* connect beforehand via a dummy socket to see if the port is ready:
doesn't work, port forwarding lets you always connect but this wont tell you if the end of the pipe is ready.
It looks to me as if the only way to achieve this is to make sure that there's a readyness probe for the debug-port, too?
[~jeffmaury] Thoughts?
was (Author: adietish):
I tried 2 approaches, but both didn't work:
* trying to catch the connection error and try again:
doesn't work, the error occurrs in a different thread
* trying to connect beforehand via a dummy socket to see if the port is ready:
doesn't work, port forwarding lets you always connect but this wont tell you if the end of the pipe is ready.
> 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
[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:
------------------------------------------
I tried 2 approaches, but both didn't work:
* trying to catch the connection error and try again:
doesn't work, the error occurrs in a different thread
* trying to connect beforehand via a dummy socket to see if the port is ready:
doesn't work, port forwarding lets you always connect but this wont tell you if the end of the pipe is ready.
> 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
[JBoss JIRA] (JBIDE-26156) "forein key name ([name]) mapped to different tables!" reading schema to import the entities from db tables.
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26156?page=com.atlassian.jira.plugi... ]
Koen Aers commented on JBIDE-26156:
-----------------------------------
[~mattgolem] Can you please add the proper DDL to create the database from which you generate the entities? Also, is this a specific problem for SAP SQL Anywhere or is it reproducible on H2 or HSQL as well?
> "forein key name ([name]) mapped to different tables!" reading schema to import the entities from db tables.
> ------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-26156
> URL: https://issues.jboss.org/browse/JBIDE-26156
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.5.3.Final
> Environment: Windows 8.1
> Eclipse version: Oxygen.3a Release (4.7.3a)
> Jboss Tools 4.5.3.Final
> SAP Sql Anywhere v.17.0.8.4103
> Reporter: Matt B
> Assignee: Koen Aers
> Priority: Critical
>
> Default name of sql anywhere's foreign key is the name of the destination table.
> If more tables link to same table, can be present di default more foreign key with same name.
> importing the entities from db tables do the error in subject
> Please manage this case.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBDS-3450) installer uses a specific JDK as default when installing JBDS; when user updates to newer rpm, jbdevstudio.ini points to non-existent path
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBDS-3450?page=com.atlassian.jira.plugin.... ]
Pavol Srna closed JBDS-3450.
----------------------------
> installer uses a specific JDK as default when installing JBDS; when user updates to newer rpm, jbdevstudio.ini points to non-existent path
> ------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3450
> URL: https://issues.jboss.org/browse/JBDS-3450
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.0.0.Beta1
> Reporter: Nick Boldt
> Assignee: Denis Golovin
> Fix For: 11.0.0.GA, 11.3.0.GA
>
> Attachments: jbds-installer_step4-jvm-selection.png
>
>
> {quote}
> (2015-06-02 16:37:24) joshuaw: maxandersen: I just ran into an issue with JBDS if you have a min
> (2015-06-02 16:38:36) joshuaw: I'm running Fedora 22 and it wanted to update, so I let it. I think I had JBDS running when I restarted. When I restarted I couldn't start JBDS.
> (2015-06-02 16:39:02) joshuaw: I got the following error: A Java Runtime Environment (JRE) or Java Development Kit (JDK)
> (2015-06-02 16:39:02) joshuaw: must be available in order to run Jbdevstudio. No Java virtual machine
> (2015-06-02 16:39:02) joshuaw: was found after searching the following locations:
> (2015-06-02 16:39:02) joshuaw: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.45-38.b14.fc22.x86_64/bin/java
> (2015-06-02 16:39:31) nickboldt: does your ~/jbdevstudio/*.ini file point to a SPECIFIC path for java?
> (2015-06-02 16:39:40) joshuaw: let me check
> 16:40
> (2015-06-02 16:40:10) nickboldt: if alternatives replaced the old JDK w/ newer one the problem is prolly that you're looking in a SPECIFIC place for JVM and Eclipse/JBDS can't find it
> (2015-06-02 16:41:37) joshuaw: though the OS update may have moved something :(
> (2015-06-02 16:42:10) nickboldt: does /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.45-38.b14.fc22.x86_64/bin/java exist?
> (2015-06-02 16:42:15) joshuaw: nickboldt: yeah, that location is in the .ini file
> (2015-06-02 16:42:28) nickboldt: and it actually exists on your disk after the update?
> (2015-06-02 16:42:29) joshuaw: nickboldt: that location does not exist
> (2015-06-02 16:42:32) nickboldt: aha
> (2015-06-02 16:42:45) nickboldt: cd /usr/lib/jvm/java-1.8.0-openjdk-1.8*
> (2015-06-02 16:42:48) nickboldt: pwd
> (2015-06-02 16:42:52) nickboldt: put that in your ini file
> (2015-06-02 16:45:46) joshuaw: I had /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.45-38.b14.fc22.x86_64/bin/java in the .ini file
> (2015-06-02 16:45:56) rbenevides is now known as rbenevides|afk
> (2015-06-02 16:46:03) joshuaw: and the system now has 1.8.0.45-39
> (2015-06-02 16:46:19) joshuaw: funny how java -version doesn't list the -39
> (2015-06-02 16:46:33) joshuaw: stupid minor minor version update
> (2015-06-02 17:46:43) maxandersen: joshuaw: any chance if you recall when you installed if you chose to use the default or specific version of a idk ?
> (2015-06-02 17:47:00) maxandersen: joshuaw: if used default it would be a bug if we added specific javavm to the ini file
> (2015-06-02 17:55:19) nickboldt: maxandersen: I never pick a specific one, just use default suggestion
> (2015-06-02 17:55:27) nickboldt: and I have $➔ cat studio/jbdevstudio.ini
> (2015-06-02 17:55:27) nickboldt: -vm
> (2015-06-02 17:55:27) nickboldt: /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.71-2.5.3.0.fc20.x86_64/jre/bin/java
> (2015-06-02 17:55:36) maxandersen: thats bad
> (2015-06-02 17:55:40) nickboldt: so... maxandersen... BUG. :(
> (2015-06-02 17:56:19) maxandersen: nickboldt: can you open bug for that one ?
> {quote}
> It's possible the installer is using the CURRENT value of alternatives path for JDK...
> {code}
> $➔ alternatives --display java
> java - status is manual.
> link currently points to /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.71-2.5.3.0.fc20.x86_64/jre/bin/java
> /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.71-2.5.3.0.fc20.x86_64/jre/bin/java - priority 170071
> {code}
> So we need to maybe point to a different path... say, in /usr/lib/jvm/jre/ ?
--
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 edited comment on JBIDE-26157 at 7/3/18 7:25 AM:
------------------------------------------------------------
[~kret11] can you be more specific as Dynamic Web Module supports versions 4.0 as of DevStudio 11.2.0.GA / JBoss Tools 4.5.2.Final ?
was (Author: jeffmaury):
@reporter can you be more specific as Dynamic Web Module supports versions 4.0 as of DevStudio 11.2.0.GA / JBoss Tools 4.5.2.Final ?
> Support for JEE8 projects
> -------------------------
>
> Key: JBIDE-26157
> URL: https://issues.jboss.org/browse/JBIDE-26157
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Reporter: Dawid Olejnik
> Assignee: Jeff MAURY
> Fix For: 4.9.x
>
>
> Need support for EARs version 8 and WARs with servlets 4.0
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months