[JBoss JIRA] (JBIDE-26158) [UPSTREAM] Server adapter: NPE when starting adapter for nodejs-mongo-persistent into Debug
by Josef Kopriva (Jira)
[ https://issues.jboss.org/browse/JBIDE-26158?page=com.atlassian.jira.plugi... ]
Josef Kopriva closed JBIDE-26158.
---------------------------------
Closing. I have not seen NPE, but handshake issue still persist: https://issues.jboss.org/browse/JBIDE-26408
Verified in:
Red Hat CodeReady Studio
Version: 12.11.0.GA
Build id: GA-v20190318-0421-B4230
Build date: 20190318-0421
> [UPSTREAM] Server adapter: NPE when starting adapter for nodejs-mongo-persistent into Debug
> --------------------------------------------------------------------------------------------
>
> Key: JBIDE-26158
> URL: https://issues.jboss.org/browse/JBIDE-26158
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.6.0.AM3
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Major
> Labels: upstream
> Fix For: 4.11.0.Final
>
> Attachments: image-2018-07-02-22-33-13-396.png, image-2018-07-02-22-49-45-246.png, image-2018-07-02-23-17-34-099.png, image-2018-07-03-00-03-56-346.png, screenshot-1.png, screenshot-2.png
>
>
> steps:
> # EXEC: launch new application wizard, choose nodejs-mongo-persistent template and finish
> # EXEC: when asked import the app and create a server adapter
> # ASSERT: server adapter is created
> # EXEC: start the server adapter
> # ASSERT: server adapter is launched
> # EXEC: restart the server adapter into Debug
> Result:
> Debuggin works, but you get the following error dialog:
> !image-2018-07-02-22-33-13-396.png!
> In the Eclipse log you'll find the following:
> {code}
> java.lang.NullPointerException
> at org.eclipse.core.internal.resources.CheckMissingNaturesListener.updateRange(CheckMissingNaturesListener.java:209)
> at org.eclipse.core.internal.resources.CheckMissingNaturesListener$3.runInWorkspace(CheckMissingNaturesListener.java:179)
> at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:60)
> {code}
> ps. project context menu: Convert > Javascript Project doesn't help.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 3 months
[JBoss JIRA] (JBIDE-26117) Connection Wizard: Parse Login command (that was copied to clipboard by the web-ui)
by Josef Kopriva (Jira)
[ https://issues.jboss.org/browse/JBIDE-26117?page=com.atlassian.jira.plugi... ]
Josef Kopriva closed JBIDE-26117.
---------------------------------
Closing. Works as expected.
Verified in:
Red Hat CodeReady Studio
Version: 12.11.0.GA
Build id: GA-v20190318-0421-B4230
Build date: 20190318-0421
> Connection Wizard: Parse Login command (that was copied to clipboard by the web-ui)
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-26117
> URL: https://issues.jboss.org/browse/JBIDE-26117
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.6.0.Final
> Reporter: Josef Kopriva
> Assignee: Josef Kopriva
> Priority: Major
> Labels: connection_wizard
> Fix For: 4.11.0.AM1
>
>
> The OpenShift web-ui provides a menu entry that creates the oc login command in your local clipboard: https://stackoverflow.com/questions/49548380/cannot-find-openshift-3-logi...
> Currently, Eclipse users would have to paste it to some notepad and use the info in it to manually create a connection. The tooling could facilitate this by parsing the clipboard and creating a connection:
> The Eclipse
> There could be a button for parsing login command in clipboard.
> Steps:
> 1. User logins in web browser in OpenShift Console.
> 2. User clicks on "Copy Login Command"
> 3. In OpenShift tooling there could be button for parse login command from clipboard.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 3 months
[JBoss JIRA] (JBIDE-26530) Connection wizard: Login command with "_" in the token results in erroneous token being used
by Josef Kopriva (Jira)
[ https://issues.jboss.org/browse/JBIDE-26530?page=com.atlassian.jira.plugi... ]
Josef Kopriva closed JBIDE-26530.
---------------------------------
Closing. Works as expected.
Verified in:
Red Hat CodeReady Studio
Version: 12.11.0.GA
Build id: GA-v20190318-0421-B4230
Build date: 20190318-0421
> Connection wizard: Login command with "_" in the token results in erroneous token being used
> --------------------------------------------------------------------------------------------
>
> Key: JBIDE-26530
> URL: https://issues.jboss.org/browse/JBIDE-26530
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.10.0.AM1
> Reporter: Andre Dietisheim
> Assignee: Josef Kopriva
> Priority: Major
> Fix For: 4.11.0.AM1
>
> Attachments: image-2019-01-23-11-51-15-428.png
>
>
> steps:
> # ASSERT: copy the following login command into your clipboard:
> {code}oc login https://api.starter-us-east-2.openshift.com --token=12345_67890{code}
> # EXEC: in Eclipse: launch connection wizard
> # EXEC: verify the token that's being used
> Result:
> The token that's being presented in the connection wizard ist *12345*
> !image-2019-01-23-11-51-15-428.png!
> Expected result:
> The token that's being used should be *12345_67890*
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 3 months
[JBoss JIRA] (JBIDE-26559) Unable to deploy a Java EE 8 project on EAP 7.2
by Josef Kopriva (Jira)
[ https://issues.jboss.org/browse/JBIDE-26559?page=com.atlassian.jira.plugi... ]
Josef Kopriva closed JBIDE-26559.
---------------------------------
I was able to deploy JavaEE8 project on EAP7.2.
Verified in:
Red Hat CodeReady Studio
Version: 12.11.0.GA
Build id: GA-v20190318-0421-B4230
Build date: 20190318-0421
> Unable to deploy a Java EE 8 project on EAP 7.2
> -----------------------------------------------
>
> Key: JBIDE-26559
> URL: https://issues.jboss.org/browse/JBIDE-26559
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server
> Affects Versions: 4.10.0.AM1
> Reporter: Mattias Andersson
> Assignee: Jeff MAURY
> Priority: Critical
> Fix For: 4.11.0.AM1
>
> Attachments: 53025554-63105e80-3461-11e9-8ec6-f7bf2f69f961.png
>
>
> Unable to deploy a Java EE 8 (servlet 4.0) project on EAP 7.2, it does not support version 4.0 of the J2EE Web module specification.
> The project implements a simple servlet war that imports the {{org.jboss.bom:jboss-eap-javaee8:7.2.0.GA:pom}}.
> I am using adapter {{3.6.2.v20190208-1835}} which I think is the latest.
> According to JBIDE-26307 the 7.1 server adapter should be be used for EAP 7.2.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 3 months