[JBoss JIRA] (JBIDE-26639) Connect wizard: have to repeatedly allow the security certificate of open.paas.redha.com
by André Dietisheim (Jira)
André Dietisheim created JBIDE-26639:
----------------------------------------
Summary: Connect wizard: have to repeatedly allow the security certificate of open.paas.redha.com
Key: JBIDE-26639
URL: https://issues.jboss.org/browse/JBIDE-26639
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Affects Versions: 4.12.0.AM1
Reporter: André Dietisheim
Attachments: image-2019-05-07-22-56-12-592.png
steps:
# EXEC: open new connection wizard
# EXEC: in server use *https://open.paas.redhat.com*
# EXEC: hit *retrieve* link
# ASSERT: dialog shows up where you should accept the self-signed certificate
!image-2019-05-07-22-56-12-592.png!
# EXEC: check *always trust "open.paas.redhat.com"* & hit *Continue*
Result:
The dialog shows up again with the *always trust "open.paas.redhat.com"* unchecked. It doesnt seem to matter if you check it: the dialog shows up again and again and again and again...
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (JBIDE-26638) Import app: error message is not clearly matching available options
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26638?page=com.atlassian.jira.plugi... ]
André Dietisheim updated JBIDE-26638:
-------------------------------------
Fix Version/s: 4.12.x
> Import app: error message is not clearly matching available options
> --------------------------------------------------------------------
>
> Key: JBIDE-26638
> URL: https://issues.jboss.org/browse/JBIDE-26638
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.12.0.AM1
> Reporter: André Dietisheim
> Priority: Major
> Fix For: 4.12.x
>
> Attachments: image-2019-05-07-22-20-07-049.png
>
>
> steps:
> # ASSERT: have an application running on OpenShift
> # ASSERT: have it imported a 1st time
> # EXEC: kill the application & create it again
> # ASSERT: import application wizard pops up so that you can import it but it's displaying an error that tells you that the git clone already exists
> Result:
> !image-2019-05-07-22-20-07-049.png!
> The error message states that the git clone already exists and tells you to *select Reuse existing repository*. In the GUI though there's no such option, there's a checkbox marked with an error that's called *Do not clone - use existing repository*
> Expected result:
> The error message should matcht the label of the checkbox so that it gets more obvious what option is suggested. ex. *select use existing repository*
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (JBIDE-26638) Import app: error message is not clearly matching available options
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26638?page=com.atlassian.jira.plugi... ]
André Dietisheim updated JBIDE-26638:
-------------------------------------
Affects Version/s: 4.12.0.AM1
(was: 4.12.x)
> Import app: error message is not clearly matching available options
> --------------------------------------------------------------------
>
> Key: JBIDE-26638
> URL: https://issues.jboss.org/browse/JBIDE-26638
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.12.0.AM1
> Reporter: André Dietisheim
> Priority: Major
> Attachments: image-2019-05-07-22-20-07-049.png
>
>
> steps:
> # ASSERT: have an application running on OpenShift
> # ASSERT: have it imported a 1st time
> # EXEC: kill the application & create it again
> # ASSERT: import application wizard pops up so that you can import it but it's displaying an error that tells you that the git clone already exists
> Result:
> !image-2019-05-07-22-20-07-049.png!
> The error message states that the git clone already exists and tells you to *select Reuse existing repository*. In the GUI though there's no such option, there's a checkbox marked with an error that's called *Do not clone - use existing repository*
> Expected result:
> The error message should matcht the label of the checkbox so that it gets more obvious what option is suggested. ex. *select use existing repository*
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (JBIDE-26638) Import app: error message is not clearly matching available options
by André Dietisheim (Jira)
André Dietisheim created JBIDE-26638:
----------------------------------------
Summary: Import app: error message is not clearly matching available options
Key: JBIDE-26638
URL: https://issues.jboss.org/browse/JBIDE-26638
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Affects Versions: 4.12.x
Reporter: André Dietisheim
Attachments: image-2019-05-07-22-20-07-049.png
steps:
# ASSERT: have an application running on OpenShift
# ASSERT: have it imported a 1st time
# EXEC: kill the application & create it again
# ASSERT: import application wizard pops up so that you can import it but it's displaying an error that tells you that the git clone already exists
Result:
!image-2019-05-07-22-20-07-049.png!
The error message states that the git clone already exists and tells you to *select Reuse existing repository*. In the GUI though there's no such option, there's a checkbox marked with an error that's called *Do not clone - use existing repository*
Expected result:
The error message should matcht the label of the checkbox so that it gets more obvious what option is suggested. ex. *select use existing repository*
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (JBIDE-26160) Server Adapter: erroneously stays in [Debugging] when you kill the pod
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-26160?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-26160:
-------------------------------
Fix Version/s: 4.12.0.AM1
(was: 4.12.0.Final)
> 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: André Dietisheim
> Assignee: Jeff MAURY
> Priority: Major
> Labels: server_adapter
> Fix For: 4.12.0.AM1
>
>
> 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. Debugging doesn't work any more because the port forwarding was stopped. To have it running again you need to restart the port forwarding for the new pod.
> 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.12.1#712002)
6 years, 11 months
[JBoss JIRA] (JBIDE-26160) Server Adapter: erroneously stays in [Debugging] when you kill the pod
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26160?page=com.atlassian.jira.plugi... ]
André Dietisheim updated JBIDE-26160:
-------------------------------------
Fix Version/s: 4.12.0.Final
(was: 4.12.x)
> 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: André Dietisheim
> Assignee: Jeff MAURY
> Priority: Major
> Labels: server_adapter
> Fix For: 4.12.0.Final
>
>
> 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. Debugging doesn't work any more because the port forwarding was stopped. To have it running again you need to restart the port forwarding for the new pod.
> 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.12.1#712002)
6 years, 11 months
[JBoss JIRA] (JBIDE-26637) Migrate sonar projects to correct organization
by Josef Kopriva (Jira)
Josef Kopriva created JBIDE-26637:
-------------------------------------
Summary: Migrate sonar projects to correct organization
Key: JBIDE-26637
URL: https://issues.jboss.org/browse/JBIDE-26637
Project: Tools (JBoss Tools)
Issue Type: Task
Components: common, openshift, server
Affects Versions: 4.12.0.AM1
Reporter: Josef Kopriva
Assignee: Josef Kopriva
Fix For: 4.12.0.AM1
Projects openshift, base and server are under wrong organization on sonarcloud, it should be migrated to correct jbosstools organization.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (JBIDE-26635) Job devstudio.product_master is red
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-26635?page=com.atlassian.jira.plugi... ]
Jeff MAURY commented on JBIDE-26635:
------------------------------------
Uploaded the missing file on devstudio.redhat.com
> Job devstudio.product_master is red
> -----------------------------------
>
> Key: JBIDE-26635
> URL: https://issues.jboss.org/browse/JBIDE-26635
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.12.0.AM1
> Environment: CentralCI
> Reporter: Josef Kopriva
> Assignee: Jeff MAURY
> Priority: Blocker
> Fix For: 4.12.0.AM1
>
>
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
> Job Fails with IO Error:
> {code:java}
> [ERROR] Failed to execute goal com.googlecode.maven-download-plugin:download-maven-plugin:1.2.0:wget (get-earlyaccess-listing) on project com.jboss.devstudio.core.central: IO Error: Could not get content -> [Help 1]
> 06:48:57 org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal com.googlecode.maven-download-plugin:download-maven-plugin:1.2.0:wget (get-earlyaccess-listing) on project com.jboss.devstudio.core.central: IO Error
> 06:48:57 at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:213)
> 06:48:57 at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:154)
> 06:48:57 at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:146)
> 06:48:57 at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
> 06:48:57 at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
> 06:48:57 at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:51)
> 06:48:57 at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
> 06:48:57 at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:309)
> 06:48:57 at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:194)
> 06:48:57 at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:107)
> 06:48:57 at org.apache.maven.cli.MavenCli.execute (MavenCli.java:955)
> 06:48:57 at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
> 06:48:57 at org.apache.maven.cli.MavenCli.main (MavenCli.java:194)
> 06:48:57 at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> 06:48:57 at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
> 06:48:57 at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
> 06:48:57 at java.lang.reflect.Method.invoke (Method.java:498)
> 06:48:57 at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:289)
> 06:48:57 at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:229)
> 06:48:57 at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:415)
> 06:48:57 at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:356)
> 06:48:57 Caused by: org.apache.maven.plugin.MojoExecutionException: IO Error
> 06:48:57 at com.googlecode.WGet.execute (WGet.java:260)
> 06:48:57 at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:134)
> 06:48:57 at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:208)
> 06:48:57 at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:154)
> 06:48:57 at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:146)
> 06:48:57 at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
> 06:48:57 at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
> 06:48:57 at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:51)
> 06:48:57 at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
> 06:48:57 at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:309)
> 06:48:57 at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:194)
> 06:48:57 at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:107)
> 06:48:57 at org.apache.maven.cli.MavenCli.execute (MavenCli.java:955)
> 06:48:57 at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
> 06:48:57 at org.apache.maven.cli.MavenCli.main (MavenCli.java:194)
> 06:48:57 at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> 06:48:57 at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
> 06:48:57 at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
> 06:48:57 at java.lang.reflect.Method.invoke (Method.java:498)
> 06:48:57 at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:289)
> 06:48:57 at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:229)
> 06:48:57 at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:415)
> 06:48:57 at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:356)
> 06:48:57 Caused by: org.apache.maven.plugin.MojoFailureException: Could not get content
> 06:48:57 at com.googlecode.WGet.execute (WGet.java:248)
> 06:48:57 at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:134)
> 06:48:57 at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:208)
> 06:48:57 at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:154)
> 06:48:57 at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:146)
> 06:48:57 at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
> 06:48:57 at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
> 06:48:57 at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:51)
> 06:48:57 at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
> 06:48:57 at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:309)
> 06:48:57 at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:194)
> 06:48:57 at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:107)
> 06:48:57 at org.apache.maven.cli.MavenCli.execute (MavenCli.java:955)
> 06:48:57 at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
> 06:48:57 at org.apache.maven.cli.MavenCli.main (MavenCli.java:194)
> 06:48:57 at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> 06:48:57 at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
> 06:48:57 at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
> 06:48:57 at java.lang.reflect.Method.invoke (Method.java:498)
> 06:48:57 at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:289)
> 06:48:57 at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:229)
> 06:48:57 at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:415)
> 06:48:57 at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:356)
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months