[JBoss JIRA] (JBIDE-26201) Application wizard: "Next" button is not enabled because of oc >= 3.11 warning
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-26201:
----------------------------------------
Summary: Application wizard: "Next" button is not enabled because of oc >= 3.11 warning
Key: JBIDE-26201
URL: https://issues.jboss.org/browse/JBIDE-26201
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.6.0.Final
Environment: F28
Red Hat Developer Studio
Version: 12.0.0.GA
Build id: GA-v20180706-1014-B2970
Build date: 20180706-1014
CDK 3.5.0
Reporter: Josef Kopriva
Assignee: Andre Dietisheim
Priority: Critical
Fix For: 4.9.0.AM1
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (JBIDE-26200) Server adapter wizard: Imported project is not filled into "Eclipse Project"
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26200?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-26200:
-------------------------------------
Labels: import_wizard server_adapter_wizard (was: )
> Server adapter wizard: Imported project is not filled into "Eclipse Project"
> ----------------------------------------------------------------------------
>
> Key: JBIDE-26200
> URL: https://issues.jboss.org/browse/JBIDE-26200
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Final
> Reporter: Andre Dietisheim
> Labels: import_wizard, server_adapter_wizard
> Fix For: 4.9.x
>
> Attachments: image-2018-07-16-14-26-26-327.png, screenshot-1.png
>
>
> steps:
> # ASSERT: make sure you have a service running on your server but it's *NOT* present in your Eclipse workspace (ex. created via the nodejs-mongo-persistent template)
> # EXEC: in Explorer: select the service of your application (ex. nodejs-mongo-persisten service) and pick "Server Adapter..." in it's context menu
> # ASSERT: server adapter wizard shows up with "Eclipse Project" empty and marked with an error
> !image-2018-07-16-14-26-26-327.png!
> # EXEC: hit "Import" to the right of the "Eclipse Project" text field
> # ASSERT: "Select Build Config" wizard shows up listing a build config to import (ex. nodejs-mongo-persistent)
> # EXEC: select the build config and finish the wizard
> # ASSERT: "Select Build Config" wizard disappears, you're back in the "Server Adapter" wizard & the project is imported to your worksapce in the background and eventually shows up in the workspace
> Result:
> "Eclipse Project" is not filled out (even though I just imported it), text field is therefore still decorated with an error
> !screenshot-1.png!
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (JBIDE-26200) Server adapter wizard: Imported project is not filled into "Eclipse Project"
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26200?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-26200:
-------------------------------------
Attachment: screenshot-1.png
> Server adapter wizard: Imported project is not filled into "Eclipse Project"
> ----------------------------------------------------------------------------
>
> Key: JBIDE-26200
> URL: https://issues.jboss.org/browse/JBIDE-26200
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Final
> Reporter: Andre Dietisheim
> Fix For: 4.9.x
>
> Attachments: image-2018-07-16-14-26-26-327.png, screenshot-1.png
>
>
> steps:
> # ASSERT: make sure you have a service running on your server but it's *NOT* present in your Eclipse workspace (ex. created via the nodejs-mongo-persistent template)
> # EXEC: in Explorer: select the service of your application (ex. nodejs-mongo-persisten service) and pick "Server Adapter..." in it's context menu
> # ASSERT: server adapter wizard shows up with "Eclipse Project" empty and marked with an error
> !image-2018-07-16-14-26-26-327.png!
> # EXEC: hit "Import" to the right of the "Eclipse Project" text field
> # ASSERT: "Select Build Config" wizard shows up listing a build config to import (ex. nodejs-mongo-persistent)
> # EXEC: select the build config and finish the wizard
> # ASSERT: "Select Build Config" wizard disappears, you're back in the "Server Adapter" wizard & the project is imported to your worksapce in the background and eventually shows up in the workspace
> Result:
> "Eclipse Project" is not filled out, still decorated with an error
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (JBIDE-26200) Server adapter wizard: Imported project is not filled into "Eclipse Project"
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26200?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-26200:
-------------------------------------
Description:
steps:
# ASSERT: make sure you have a service running on your server but it's *NOT* present in your Eclipse workspace (ex. created via the nodejs-mongo-persistent template)
# EXEC: in Explorer: select the service of your application (ex. nodejs-mongo-persisten service) and pick "Server Adapter..." in it's context menu
# ASSERT: server adapter wizard shows up with "Eclipse Project" empty and marked with an error
!image-2018-07-16-14-26-26-327.png!
# EXEC: hit "Import" to the right of the "Eclipse Project" text field
# ASSERT: "Select Build Config" wizard shows up listing a build config to import (ex. nodejs-mongo-persistent)
# EXEC: select the build config and finish the wizard
# ASSERT: "Select Build Config" wizard disappears, you're back in the "Server Adapter" wizard & the project is imported to your worksapce in the background and eventually shows up in the workspace
Result:
"Eclipse Project" is not filled out (even though I just imported it), text field is therefore still decorated with an error
!screenshot-1.png!
was:
steps:
# ASSERT: make sure you have a service running on your server but it's *NOT* present in your Eclipse workspace (ex. created via the nodejs-mongo-persistent template)
# EXEC: in Explorer: select the service of your application (ex. nodejs-mongo-persisten service) and pick "Server Adapter..." in it's context menu
# ASSERT: server adapter wizard shows up with "Eclipse Project" empty and marked with an error
!image-2018-07-16-14-26-26-327.png!
# EXEC: hit "Import" to the right of the "Eclipse Project" text field
# ASSERT: "Select Build Config" wizard shows up listing a build config to import (ex. nodejs-mongo-persistent)
# EXEC: select the build config and finish the wizard
# ASSERT: "Select Build Config" wizard disappears, you're back in the "Server Adapter" wizard & the project is imported to your worksapce in the background and eventually shows up in the workspace
Result:
"Eclipse Project" is not filled out, still decorated with an error
> Server adapter wizard: Imported project is not filled into "Eclipse Project"
> ----------------------------------------------------------------------------
>
> Key: JBIDE-26200
> URL: https://issues.jboss.org/browse/JBIDE-26200
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Final
> Reporter: Andre Dietisheim
> Fix For: 4.9.x
>
> Attachments: image-2018-07-16-14-26-26-327.png, screenshot-1.png
>
>
> steps:
> # ASSERT: make sure you have a service running on your server but it's *NOT* present in your Eclipse workspace (ex. created via the nodejs-mongo-persistent template)
> # EXEC: in Explorer: select the service of your application (ex. nodejs-mongo-persisten service) and pick "Server Adapter..." in it's context menu
> # ASSERT: server adapter wizard shows up with "Eclipse Project" empty and marked with an error
> !image-2018-07-16-14-26-26-327.png!
> # EXEC: hit "Import" to the right of the "Eclipse Project" text field
> # ASSERT: "Select Build Config" wizard shows up listing a build config to import (ex. nodejs-mongo-persistent)
> # EXEC: select the build config and finish the wizard
> # ASSERT: "Select Build Config" wizard disappears, you're back in the "Server Adapter" wizard & the project is imported to your worksapce in the background and eventually shows up in the workspace
> Result:
> "Eclipse Project" is not filled out (even though I just imported it), text field is therefore still decorated with an error
> !screenshot-1.png!
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (JBIDE-26200) Server adapter wizard: Imported project is not filled into "Eclipse Project"
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-26200:
----------------------------------------
Summary: Server adapter wizard: Imported project is not filled into "Eclipse Project"
Key: JBIDE-26200
URL: https://issues.jboss.org/browse/JBIDE-26200
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.1.Final
Reporter: Andre Dietisheim
Fix For: 4.9.x
Attachments: image-2018-07-16-14-26-26-327.png
steps:
# ASSERT: make sure you have a service running on your server but it's *NOT* present in your Eclipse workspace (ex. created via the nodejs-mongo-persistent template)
# EXEC: in Explorer: select the service of your application (ex. nodejs-mongo-persisten service) and pick "Server Adapter..." in it's context menu
# ASSERT: server adapter wizard shows up with "Eclipse Project" empty and marked with an error
!image-2018-07-16-14-26-26-327.png!
# EXEC: hit "Import" to the right of the "Eclipse Project" text field
# ASSERT: "Select Build Config" wizard shows up listing a build config to import (ex. nodejs-mongo-persistent)
# EXEC: select the build config and finish the wizard
# ASSERT: "Select Build Config" wizard disappears, you're back in the "Server Adapter" wizard & the project is imported to your worksapce in the background and eventually shows up in the workspace
Result:
"Eclipse Project" is not filled out, still decorated with an error
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (JBIDE-26199) No response when adding a discovery path for the 2nd time / removing a non existing path
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26199?page=com.atlassian.jira.plugi... ]
Jan Richter updated JBIDE-26199:
--------------------------------
Description:
server/addDiscoveryPath should have some way of notifying the client when it's trying to add a discovery path that has already been added.
same goes for server/removeDiscoveryPath when the path doesn't exist on the server
was:server/addDiscoveryPath should have some way of notifying the client when it's trying to add a discovery path that has already been added.
Summary: No response when adding a discovery path for the 2nd time / removing a non existing path (was: No response when adding a discovery path for the 2nd time)
> No response when adding a discovery path for the 2nd time / removing a non existing path
> ----------------------------------------------------------------------------------------
>
> Key: JBIDE-26199
> URL: https://issues.jboss.org/browse/JBIDE-26199
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: stack-server-protocol
> Affects Versions: 4.6.0.Final
> Reporter: Jan Richter
> Assignee: Rob Stryker
>
> server/addDiscoveryPath should have some way of notifying the client when it's trying to add a discovery path that has already been added.
> same goes for server/removeDiscoveryPath when the path doesn't exist on the server
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months