[JBoss JIRA] (JBIDE-26164) internal packages are a mess
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26164?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-26164:
-------------------------------------
Attachment: (was: image-2018-07-04-15-41-32-687.png)
> internal packages are a mess
> ----------------------------
>
> Key: JBIDE-26164
> URL: https://issues.jboss.org/browse/JBIDE-26164
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.6.0.AM3
> Reporter: Andre Dietisheim
> Priority: Minor
> Fix For: 4.9.x
>
> Attachments: image-2018-07-04-15-42-01-395.png
>
>
> Our package structure is a mess, especially internal ones are wrong.
> Ex. org.jboss.tools.openshift ui:
> There are 2 internal packages:
> * org.jboss.tools.openshift.internal.ui
> * org.jboss.tools.openshift.ui.internal
> !image-2018-07-04-15-42-01-395.png!
> Internal packages have to follow the base plugin name.
> * org.jboss.tools.openshift.internal.ui: *{color:green}CORRECT{color}*
> * org.jboss.tools.openshift.ui.internal: *{color:red}WRONG{color}*
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-26163) Implements Launcher model from API endpoint
by Jeff MAURY (JIRA)
Jeff MAURY created JBIDE-26163:
----------------------------------
Summary: Implements Launcher model from API endpoint
Key: JBIDE-26163
URL: https://issues.jboss.org/browse/JBIDE-26163
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Affects Versions: 4.6.0.Final
Reporter: Jeff MAURY
Assignee: Jeff MAURY
Fix For: 4.9.0.AM1
In order to implement a Launcher based project wizard, we should first implement the Launcher metadata loading inside JBoss Tools
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-26160) Server Adapter: erroneously stays in [Debugging] when you kill the pod
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26160?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-26160:
-------------------------------------
Description:
steps:
# EXEC: create an application (via ex. nodejs-mongo-persistent template), import the project and create a server adapter for it
# ASSERT: server adapter is created
# EXEC: start the server adapter in Debugging
# ASSERT: sever adapter is in *[Debugging, Synchronized]* state
# ASSERT: select pod and pick "Port Forwarding..." and it states that the forwarding is started
# EXEC: in Explorer: select the pod for your service and pick "Delete"
# ASSERT: pod gets deleted and recreated
# ASSERT: select pod and pick "Port Forwarding..." and it states that the forwarding is stopped
Result:
The server adapter still says that is is *[Debugging, Synchronized]*, but debugging is not working any more. The new pod is not running in debug (dev-) mode any more. To have it running again you need to restart the server adapter into debug, which will re-create a new pod in debug-mode.
Expected result:
Server adapter should get out of debugging and back into normal run mode *[Started, Synchronized]*.
was:
steps:
# EXEC: create an application (via ex. nodejs-mongo-persistent template), import the project and create a server adapter for it
# ASSERT: server adapter is created
# EXEC: start the server adapter in Debugging
# ASSERT: sever adapter is in *[Debugging, Synchronized]* state
# ASSERT: select pod and pick "Port Forwarding..." and it states that the forwarding is started
# EXEC: in Explorer: select the pod for your service and pick "Delete"
# ASSERT: pod gets deleted and recreated
# ASSERT: select pod and pick "Port Forwarding..." and it states that the forwarding is stopped
Result:
The server adapter still says that is is *[Debugging, Synchronized]*, but debugging is not working any more. The new pod is not running in debug (dev-) mode any more. To have it running again you need to restart the server adapter into debug, which will re-create a new pod in debug-mode.
Expected result:
Server adapter should get out of debugging and back into normal run mode.
> Server Adapter: erroneously stays in [Debugging] when you kill the pod
> ----------------------------------------------------------------------
>
> Key: JBIDE-26160
> URL: https://issues.jboss.org/browse/JBIDE-26160
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.6.0.AM3
> Reporter: Andre Dietisheim
> Labels: server_adapter
>
> steps:
> # EXEC: create an application (via ex. nodejs-mongo-persistent template), import the project and create a server adapter for it
> # ASSERT: server adapter is created
> # EXEC: start the server adapter in Debugging
> # ASSERT: sever adapter is in *[Debugging, Synchronized]* state
> # ASSERT: select pod and pick "Port Forwarding..." and it states that the forwarding is started
> # EXEC: in Explorer: select the pod for your service and pick "Delete"
> # ASSERT: pod gets deleted and recreated
> # ASSERT: select pod and pick "Port Forwarding..." and it states that the forwarding is stopped
> Result:
> The server adapter still says that is is *[Debugging, Synchronized]*, but debugging is not working any more. The new pod is not running in debug (dev-) mode any more. To have it running again you need to restart the server adapter into debug, which will re-create a new pod in debug-mode.
> Expected result:
> Server adapter should get out of debugging and back into normal run mode *[Started, Synchronized]*.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-26160) Server Adapter: erroneously keeps debugging when you kill the pod
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26160?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-26160:
-------------------------------------
Summary: Server Adapter: erroneously keeps debugging when you kill the pod (was: Server Adapter: erroneously keeps being in Debugging when you kill the pod)
> Server Adapter: erroneously keeps debugging when you kill the pod
> -----------------------------------------------------------------
>
> Key: JBIDE-26160
> URL: https://issues.jboss.org/browse/JBIDE-26160
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.6.0.AM3
> Reporter: Andre Dietisheim
> Labels: server_adapter
>
> steps:
> # EXEC: create an application (via ex. nodejs-mongo-persistent template), import the project and create a server adapter for it
> # ASSERT: server adapter is created
> # EXEC: start the server adapter in Debugging
> # ASSERT: sever adapter is in *[Debugging, Synchronized]* state
> # ASSERT: select pod and pick "Port Forwarding..." and it states that the forwarding is started
> # EXEC: in Explorer: select the pod for your service and pick "Delete"
> # ASSERT: pod gets deleted and recreated
> # ASSERT: select pod and pick "Port Forwarding..." and it states that the forwarding is stopped
> Result:
> The server adapter still says that is is *[Debugging, Synchronized]*, but debugging is not working any more. The new pod is not running in debug (dev-) mode any more. To have it running again you need to restart the server adapter into debug, which will re-create a new pod in debug-mode.
> Expected result:
> Server adapter should get out of debugging and back into normal run mode.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-26160) Server Adapter: erroneously stays in [Debugging] when you kill the pod
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26160?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-26160:
-------------------------------------
Summary: Server Adapter: erroneously stays in [Debugging] when you kill the pod (was: Server Adapter: erroneously keeps debugging when you kill the pod)
> Server Adapter: erroneously stays in [Debugging] when you kill the pod
> ----------------------------------------------------------------------
>
> Key: JBIDE-26160
> URL: https://issues.jboss.org/browse/JBIDE-26160
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.6.0.AM3
> Reporter: Andre Dietisheim
> Labels: server_adapter
>
> steps:
> # EXEC: create an application (via ex. nodejs-mongo-persistent template), import the project and create a server adapter for it
> # ASSERT: server adapter is created
> # EXEC: start the server adapter in Debugging
> # ASSERT: sever adapter is in *[Debugging, Synchronized]* state
> # ASSERT: select pod and pick "Port Forwarding..." and it states that the forwarding is started
> # EXEC: in Explorer: select the pod for your service and pick "Delete"
> # ASSERT: pod gets deleted and recreated
> # ASSERT: select pod and pick "Port Forwarding..." and it states that the forwarding is stopped
> Result:
> The server adapter still says that is is *[Debugging, Synchronized]*, but debugging is not working any more. The new pod is not running in debug (dev-) mode any more. To have it running again you need to restart the server adapter into debug, which will re-create a new pod in debug-mode.
> Expected result:
> Server adapter should get out of debugging and back into normal run mode.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[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 edited comment on JBIDE-26157 at 7/4/18 7:30 AM:
---------------------------------------------------------------
I cannot add artifact to server deployments feature when built newest .war:
!screenshot-1.png|thumbnail!
was (Author: kret11):
I cannot add artifact to server deployments feature:
!screenshot-1.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
>
>
> 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
[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 edited comment on JBIDE-26157 at 7/4/18 7:30 AM:
---------------------------------------------------------------
[~jeffmaury]
I cannot add artifact to server deployments feature when built newest .war:
!screenshot-1.png|thumbnail!
was (Author: kret11):
I cannot add artifact to server deployments feature when built newest .war:
!screenshot-1.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
>
>
> 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