[JBoss JIRA] (JBIDE-23360) Remember selected route in ambiguous routing does not work
by Marián Labuda (JIRA)
Marián Labuda created JBIDE-23360:
-------------------------------------
Summary: Remember selected route in ambiguous routing does not work
Key: JBIDE-23360
URL: https://issues.jboss.org/browse/JBIDE-23360
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.4.2.AM2
Reporter: Marián Labuda
When selecting Show In - Web Browser on a project with more services, routing is ambiguous. There is shown a shell "Select Route" with a checkbox "Remember selected route". This checkbox does not work. If I check it and then click OK button, I get the same prompt again next time I select Show In - Web Browser context menu item.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-23360) Remember selected route in ambiguous routing does not work
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23360?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-23360:
----------------------------------
Labels: openshift_v3 (was: )
> Remember selected route in ambiguous routing does not work
> ----------------------------------------------------------
>
> Key: JBIDE-23360
> URL: https://issues.jboss.org/browse/JBIDE-23360
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.2.AM2
> Reporter: Marián Labuda
> Labels: openshift_v3
>
> When selecting Show In - Web Browser on a project with more services, routing is ambiguous. There is shown a shell "Select Route" with a checkbox "Remember selected route". This checkbox does not work. If I check it and then click OK button, I get the same prompt again next time I select Show In - Web Browser context menu item.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-23353) Deploy Docker Wizard: Enable checking "Used by route" checkbox by mouse click
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23353?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-23353:
------------------------------------------
I agree that this isnt user-friendly, but still not cirical. Downgrading to Major.
> Deploy Docker Wizard: Enable checking "Used by route" checkbox by mouse click
> -----------------------------------------------------------------------------
>
> Key: JBIDE-23353
> URL: https://issues.jboss.org/browse/JBIDE-23353
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.2.AM2
> Reporter: Marián Labuda
> Priority: Critical
> Labels: deploy_docker_wizard, openshift_v3
>
> In Deploy Image to OpenShift on wizard page with routing settings there is a table with port mapping. There is a table cell with checkbox to be used by routing. This is not editable by clicking on the cell. User is forced to open dialog to edit port mapping, manually click on a checkbox to use for routing and confirm dialog. This is pretty user unfriendly. It should be enabled to click on the cell and have checkbox checked/unchecked.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-23353) Deploy Docker Wizard: Enable checking "Used by route" checkbox by mouse click
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23353?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23353:
-------------------------------------
Priority: Major (was: Critical)
> Deploy Docker Wizard: Enable checking "Used by route" checkbox by mouse click
> -----------------------------------------------------------------------------
>
> Key: JBIDE-23353
> URL: https://issues.jboss.org/browse/JBIDE-23353
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.2.AM2
> Reporter: Marián Labuda
> Labels: deploy_docker_wizard, openshift_v3
>
> In Deploy Image to OpenShift on wizard page with routing settings there is a table with port mapping. There is a table cell with checkbox to be used by routing. This is not editable by clicking on the cell. User is forced to open dialog to edit port mapping, manually click on a checkbox to use for routing and confirm dialog. This is pretty user unfriendly. It should be enabled to click on the cell and have checkbox checked/unchecked.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-23359) Validation of exception handler - handlers must not throw exceptions
by Lukáš Valach (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23359?page=com.atlassian.jira.plugi... ]
Lukáš Valach updated JBIDE-23359:
---------------------------------
Affects Version/s: 4.4.2.AM2
(was: 4.4.2.AM1)
> Validation of exception handler - handlers must not throw exceptions
> --------------------------------------------------------------------
>
> Key: JBIDE-23359
> URL: https://issues.jboss.org/browse/JBIDE-23359
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: cdi-extensions
> Affects Versions: 4.4.2.AM2
> Reporter: Lukáš Valach
>
> As stated in the deltaspike documentation, exception handlers must not throw checked exceptions, and should avoid throwing unchecked exceptions.
> ??Handlers must not throw checked exceptions, and should avoid throwing unchecked exceptions. Should a handler throw an unchecked exception it will propagate up the stack and all handling done via DeltaSpike will cease. Any exception that was being handled will be lost.??
> I checked that throwing exceptions from handler really causes problems.
> I suggest to add validation which could display error when user attempts to throw checked exception and warning when try to throw unchecked exception.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-23359) Validation of exception handler - handlers must not throw exceptions
by Lukáš Valach (JIRA)
Lukáš Valach created JBIDE-23359:
------------------------------------
Summary: Validation of exception handler - handlers must not throw exceptions
Key: JBIDE-23359
URL: https://issues.jboss.org/browse/JBIDE-23359
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: cdi-extensions
Affects Versions: 4.4.2.AM1
Reporter: Lukáš Valach
As stated in the deltaspike documentation, exception handlers must not throw checked exceptions, and should avoid throwing unchecked exceptions.
??Handlers must not throw checked exceptions, and should avoid throwing unchecked exceptions. Should a handler throw an unchecked exception it will propagate up the stack and all handling done via DeltaSpike will cease. Any exception that was being handled will be lost.??
I checked that throwing exceptions from handler really causes problems.
I suggest to add validation which could display error when user attempts to throw checked exception and warning when try to throw unchecked exception.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-22803) Explorer: When OS projects are created and deleted, seems Openshift explorer restores non existing values
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22803?page=com.atlassian.jira.plugi... ]
Jeff Cantrill commented on JBIDE-22803:
---------------------------------------
I believe that is correct. To make it easier, we should update the restclient to throw an UnsupportedOperationException when its not supported. This would make it more obvious for jbt to consume.
> Explorer: When OS projects are created and deleted, seems Openshift explorer restores non existing values
> ---------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-22803
> URL: https://issues.jboss.org/browse/JBIDE-22803
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.AM2
> Reporter: Jeff MAURY
> Assignee: Dmitrii Bocharov
> Labels: explorer, openshift, openshift_v3
> Fix For: 4.4.2.AM2
>
> Attachments: after application creation.png, after build finished.png, Openshift Web Console.png, screenshot-1.png
>
>
> EXEC: create an Openshift project
> EXEC: expand it
> EXEC: Create an application in this project (nodejs-example)
> ASSERT: wait for the pod to be available
> EXEC: delete the Openshit project
> EXEC: create an Openshift project (using the same name. You may have to repeat this step as you may got error that it still exists)
> EXEC: expand it
> EXEC: Create an application in this project (nodejs-example)
> EXEC: expand the nodejs-example node
> ASSERT: you should see 2 pods the old one and the build pod you just created: [^screenshot-1.png]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-23277) Update arquillian bot integration tests - to resolve intermittent timing issue
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23277?page=com.atlassian.jira.plugi... ]
Len DiMaggio closed JBIDE-23277.
--------------------------------
> Update arquillian bot integration tests - to resolve intermittent timing issue
> ------------------------------------------------------------------------------
>
> Key: JBIDE-23277
> URL: https://issues.jboss.org/browse/JBIDE-23277
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: qa
> Affects Versions: 4.4.2.AM1
> Reporter: Len DiMaggio
> Assignee: Len DiMaggio
> Priority: Minor
> Fix For: 4.4.2.AM1
>
>
> Recent updates to tests have exposed another timing issue that had been masked - need to increase the timeout for Central to load as this is causing intermittent timeouts and test failures:
> org.jboss.reddeer.common.exception.WaitTimeoutExpiredException: Timeout after: 10 s.: Waiting for Central to load
> at org.jboss.reddeer.common.wait.AbstractWait.timeoutExceeded(AbstractWait.java:183)
> at org.jboss.reddeer.common.wait.AbstractWait.wait(AbstractWait.java:136)
> at org.jboss.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:101)
> at org.jboss.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:71)
> at org.jboss.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:56)
> at org.jboss.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:44)
> at org.jboss.reddeer.common.wait.WaitUntil.<init>(WaitUntil.java:35)
> at org.jboss.tools.arquillian.ui.bot.test.cruiserView.BasicArquilliaCruiserTest.setup(BasicArquilliaCruiserTest.java:48)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-23152) NPE when deploying image with ENV with no value
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23152?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-23152.
---------------------------------
Verified in DevStudio 10.2.0.AM2 build AM2-v20161014-0456-B6202.
> NPE when deploying image with ENV with no value
> -----------------------------------------------
>
> Key: JBIDE-23152
> URL: https://issues.jboss.org/browse/JBIDE-23152
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.Final
> Reporter: Jeff MAURY
> Assignee: Dmitrii Bocharov
> Labels: openshift, openshift_v3
> Fix For: 4.4.2.AM2
>
> Attachments: Dockerfile
>
>
> EXEC: first deploy jboss-eap64-openshift builder image
> ASSERT: wait until deployment is finished
> EXEC: delete the deployment
> EXEC: deploy the image that has been produced (172.30.159.75:5000/ddd/jboss-eap64-openshift:latest if my project was ddd)
> ASSERT: error dialog is shown NPE is generated because image has one or several env variables with no value (XXXX=)
> As this first scenario seems to be valid only if you're working with CDK2.2 and no proxy set, here is a scenario valid for all versions of CDK:
> ASSERT: have a Docker file with an empty ENV value. You can use https://github.com/redhat-helloworld-msa/aloha and edit the Docker file and add the following statement:
> {quote}ENV NOVALUE ""{quote}
> EXEC: build the Docker image on the CDK Docker connection. If you use aloha (https://github.com/redhat-helloworld-msa/aloha), then you must beforehand run the "mvn package" command to get binary artifacts being produced. Select the Dockerfile, click *_Run As -> Docker Image Build_*, select the CDK Docker connection and give *_msa/aloha:1_* as image name
> ASSERT: your Docker image has been generated
> EXEC: from the Openshift explorer, select the *_Deploy Docker Image_*, then select the CDK Docker Connection, then click on *_Browse_* and select the *_msa/aloha:1_* image, then click on the Next button
> ASSERT: you should get an error
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-23284) NullPointerException in SubsystemModel.getSubsystemMappings
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23284?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-23284.
---------------------------------
> NullPointerException in SubsystemModel.getSubsystemMappings
> -----------------------------------------------------------
>
> Key: JBIDE-23284
> URL: https://issues.jboss.org/browse/JBIDE-23284
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Reporter: Automated Error Reporting Bot
> Assignee: Rob Stryker
> Fix For: 4.4.2.AM2
>
>
> The following problem was reported via the automated error reporting:
> Message: Problems occurred when invoking code from plug-in: "org.eclipse.ui.workbench".
> {noformat}
> java.lang.NullPointerException: null
> at org.jboss.ide.eclipse.as.wtp.core.server.behavior.SubsystemModel.getSubsystemMappings(SubsystemModel.java:259)
> at org.jboss.ide.eclipse.as.wtp.core.server.behavior.SubsystemModel.getSubsystemMappingForCreation(SubsystemModel.java:358)
> at org.jboss.ide.eclipse.as.wtp.core.server.behavior.SubsystemModel.createSubsystemController(SubsystemModel.java:449)
> at org.jboss.ide.eclipse.as.wtp.core.server.behavior.SubsystemModel.createControllerForSubsystem(SubsystemModel.java:303)
> at org.jboss.ide.eclipse.as.wtp.core.server.behavior.ServerProfileModel$ServerProfile.getController(ServerProfileModel.java:355)
> at org.jboss.ide.eclipse.as.wtp.core.server.behavior.ServerProfileModel$ServerProfile.getController(ServerProfileModel.java:348)
> at org.jboss.ide.eclipse.as.wtp.core.server.behavior.ServerProfileModel.getController(ServerProfileModel.java:183)
> at org.jboss.ide.eclipse.as.wtp.core.server.behavior.ProfileServerBehavior.getController(ProfileServerBehavior.java:59)
> at org.jboss.ide.eclipse.as.wtp.core.server.behavior.CachedPublisherProfileBehavior.getPublishController(CachedPublisherProfileBehavior.java:35)
> at org.jboss.ide.eclipse.as.wtp.core.server.behavior.ControllableServerBehavior.canPublish(ControllableServerBehavior.java:297)
> at org.eclipse.wst.server.core.internal.Server.canPublish(Server.java:1218)
> at org.eclipse.wst.server.core.internal.Server.shouldPublish(Server.java:1231)
> at org.eclipse.wst.server.ui.internal.cnf.ServerDecorator.getServerStatusLabel(ServerDecorator.java:139)
> at org.eclipse.wst.server.ui.internal.cnf.ServerDecorator.decorate(ServerDecorator.java:73)
> at org.eclipse.ui.internal.decorators.LightweightDecoratorDefinition.decorate(LightweightDecoratorDefinition.java:273)
> at org.eclipse.ui.internal.decorators.LightweightDecoratorManager$LightweightRunnable.run(LightweightDecoratorManager.java:83)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.decorators.LightweightDecoratorManager.decorate(LightweightDecoratorManager.java:367)
> at org.eclipse.ui.internal.decorators.LightweightDecoratorManager.getDecorations(LightweightDecoratorManager.java:349)
> at org.eclipse.ui.internal.decorators.DecorationScheduler$1.ensureResultCached(DecorationScheduler.java:372)
> at org.eclipse.ui.internal.decorators.DecorationScheduler$1.run(DecorationScheduler.java:332)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {noformat}
> Bundles:
> | org.eclipse.core.jobs | 3.7.0.v20150330-2103 | 3.8.0.v20160509-0411 |
> | org.eclipse.core.runtime | 3.11.1.v20150903-1804 | 3.12.0.v20160606-1342 |
> | org.eclipse.jface | 3.12.0.v20160518-1929 | 3.12.0.v20160518-1929 |
> | org.eclipse.swt | 3.105.0.v20160603-0902 | 3.105.0.v20160603-0902 |
> | org.eclipse.ui | 3.107.0.v20150507-1945 | 3.108.0.v20160518-1929 |
> | org.eclipse.ui.navigator | 3.6.100.v20160518-1929 | 3.6.100.v20160518-1929 |
> | org.eclipse.wst.server.core | 1.8.0.v201601132216 | 1.8.100.v201605201456 |
> | org.eclipse.wst.server.ui | 1.5.202.v201602111638 | 1.5.304.v201605121430 |
> | org.jboss.ide.eclipse.as.wtp.core | 3.1.0.Final-v20150924-2222-B46 | 3.2.0.Final-v20160614-2020-B9 |
> Operating Systems:
> | Linux | 3.2.0 | 4.6.3.fc24 |
> | Windows | 6.1.0 | 10.0.0 |
> The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/571d2d0be4b0e9dd9c...] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months