[JBoss JIRA] (JBIDE-21974) Wrong service is preselected when creating a new OS3 server adapter from context menu of a service
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21974?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-21974.
---------------------------------
Verified in Red Hat Developer Studio 10.0.0.Alpha1 B5264.
> Wrong service is preselected when creating a new OS3 server adapter from context menu of a service
> --------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21974
> URL: https://issues.jboss.org/browse/JBIDE-21974
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Labels: openshift_v3, server_adapter_wizard
> Fix For: 4.4.0.Alpha1
>
>
> When I am creating a new OpenShift 3 server adapter from context menu of a service in OpenShift explorer view and I am having several projects and at least 2 same services (names must be equal) in different projects, then in New OS 3 Server Wizard is wrong service. This is happening when I am trying to create a server adapter from context menu of a service which is lower (in order of tree items under an OpenShift 3 connection) then a service with same name.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-21975) Server Adapter wizard: route is not changed when I select a different service
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21975?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-21975.
---------------------------------
Verified in Red Hat Developer Studio 10.0.0.Alpha1 B5264.
> Server Adapter wizard: route is not changed when I select a different service
> -----------------------------------------------------------------------------
>
> Key: JBIDE-21975
> URL: https://issues.jboss.org/browse/JBIDE-21975
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.4.0.Alpha1
>
>
> # ASSERT: have a project with at least 2 services and 2 routes (ex. nodejs-example and eap-app services)
> # EXEC: launch OpenShift 3 Server Adapter wizard
> # ASSERT: eap-app service is selected
> # ASSERT: accordingly *eap-app* route is selected in "Use Route:"
> # EXEC: select eap-app service
> Result:
> "Use Route" is still set to *eap-app* route
> Expected result:
> "Use Route" should be set to *nodejs-example* route
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBDS-3877) can't import bigger maven/git project to jbds
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3877?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov reassigned JBDS-3877:
------------------------------------
Assignee: Viacheslav Kabanovich
> can't import bigger maven/git project to jbds
> ---------------------------------------------
>
> Key: JBDS-3877
> URL: https://issues.jboss.org/browse/JBDS-3877
> Project: Red Hat Developer Studio (DevStudio)
> Issue Type: Bug
> Components: maven
> Affects Versions: 9.1.0.GA
> Reporter: Josef Ludvicek
> Assignee: Viacheslav Kabanovich
> Attachments: jbds-import-camel-stuck.png, jbds-import-camel1.png
>
>
> JBDS can't import sources of Apache Camel (maven project)
> https://github.com/apache/camel
> Steps to reproduce:
> Clone it's git repo
> {code}
> git clone git@github.com:apache/camel.git
> {code}
> In jbds File -> Import Existing maven project
> Unselect "resolve workspace projects"
> Watch all CPU cores load on 100 % (tested on lenovo T440s / Intel i7 / Fedora 23)
> Wait for error message (~20 minutes)
> {code}
> An internal error occurred during: "Importing Maven projects".
> Java heap space
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBDS-3877) can't import bigger maven/git project to jbds
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3877?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov commented on JBDS-3877:
--------------------------------------
Set "maven" component for this issue but it can be anything.
[~scabanovich] can you please try to reproduce it and see what's going on?
> can't import bigger maven/git project to jbds
> ---------------------------------------------
>
> Key: JBDS-3877
> URL: https://issues.jboss.org/browse/JBDS-3877
> Project: Red Hat Developer Studio (DevStudio)
> Issue Type: Bug
> Components: maven
> Affects Versions: 9.1.0.GA
> Reporter: Josef Ludvicek
> Attachments: jbds-import-camel-stuck.png, jbds-import-camel1.png
>
>
> JBDS can't import sources of Apache Camel (maven project)
> https://github.com/apache/camel
> Steps to reproduce:
> Clone it's git repo
> {code}
> git clone git@github.com:apache/camel.git
> {code}
> In jbds File -> Import Existing maven project
> Unselect "resolve workspace projects"
> Watch all CPU cores load on 100 % (tested on lenovo T440s / Intel i7 / Fedora 23)
> Wait for error message (~20 minutes)
> {code}
> An internal error occurred during: "Importing Maven projects".
> Java heap space
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBDS-3877) can't import bigger maven/git project to jbds
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3877?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov updated JBDS-3877:
---------------------------------
Component/s: maven
> can't import bigger maven/git project to jbds
> ---------------------------------------------
>
> Key: JBDS-3877
> URL: https://issues.jboss.org/browse/JBDS-3877
> Project: Red Hat Developer Studio (DevStudio)
> Issue Type: Bug
> Components: maven
> Affects Versions: 9.1.0.GA
> Reporter: Josef Ludvicek
> Attachments: jbds-import-camel-stuck.png, jbds-import-camel1.png
>
>
> JBDS can't import sources of Apache Camel (maven project)
> https://github.com/apache/camel
> Steps to reproduce:
> Clone it's git repo
> {code}
> git clone git@github.com:apache/camel.git
> {code}
> In jbds File -> Import Existing maven project
> Unselect "resolve workspace projects"
> Watch all CPU cores load on 100 % (tested on lenovo T440s / Intel i7 / Fedora 23)
> Wait for error message (~20 minutes)
> {code}
> An internal error occurred during: "Importing Maven projects".
> Java heap space
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months