[JBoss JIRA] (JBIDE-22227) Hotcode replace fails on local wildfly if breakpoint is set
by Thomas Mäder (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22227?page=com.atlassian.jira.plugi... ]
Thomas Mäder commented on JBIDE-22227:
--------------------------------------
Installing a breakpoint in a class creates a hard reference to the class, it seems. In the end, it's the same issue as the the HCR: you can't tell a garbage class from a live one. Hopefully, someone from the Open JDK or jdt-debug world can shed some light.
> Hotcode replace fails on local wildfly if breakpoint is set
> -----------------------------------------------------------
>
> Key: JBIDE-22227
> URL: https://issues.jboss.org/browse/JBIDE-22227
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.4.0.Alpha1
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.4.0.Alpha1
>
>
> When debugging a local wildfly server with a deployed servlet, making a breaking change such as method name or signature will fail.
> This will pop up a dialog asking to restart the module or the server, which is expected. However, after that, non-breaking changes will still also pop up the hotcode-failed dialog, when it shouldn't.
> Workflow:
> 1) Create a dynamic web project with simple servlet
> 2) Start a wildfly 10 in debug mode and deploy the web project
> 3) Run-on-server the servlet object and verify it shows expected output
> 4) Set a breakpoint inside the doGet() method
> 5) refresh browser (breakpoint gets hit), press play
> 6) Make a non-breaking change (change text inside doGet())
> 7) refresh website, verify breakpoint is hit, website content is updated
> 8) make a breaking change by adding a new method
> 9) hotcode-replace dialog appears. Press 'restart module'
> 10) refresh web browser, verify breakpoint is hit, output has changed as expected
> 11) make a non-breaking change in output of doGet()
> 12) ASSERT: hotcode replace dialog does NOT show - THIS STEP FAILS
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22289) Deploy Docker Wizard: Suggestion box of docker images is still visible on the next wizard page
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22289?page=com.atlassian.jira.plugi... ]
Fred Bricon reassigned JBIDE-22289:
-----------------------------------
Story Points: 1
Sprint: devex #113 April 2016
Priority: Minor (was: Critical)
Assignee: Viacheslav Kabanovich
> Deploy Docker Wizard: Suggestion box of docker images is still visible on the next wizard page
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-22289
> URL: https://issues.jboss.org/browse/JBIDE-22289
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Environment: Fedora 22, GTK 3.
> Reporter: Marián Labuda
> Assignee: Viacheslav Kabanovich
> Priority: Minor
> Labels: docker, openshift_v3
> Fix For: 4.4.0.Alpha2
>
>
> If I start typing name of image in Deploy Image to OpenShift wizard in the Image Name: text widget, suggestions are provided (autocomplete). If I select an image in this suggestion box by hitting Enter key, and then click by mouse on Next button, the next wizard page (Deployment Configuration and Scalability) shows this suggestion box again and on top, even it disappeared in previous wizard page.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22293) Deploy Docker Image: Next gets enabled after canceling Manage Projects
by Viacheslav Kabanovich (JIRA)
Viacheslav Kabanovich created JBIDE-22293:
---------------------------------------------
Summary: Deploy Docker Image: Next gets enabled after canceling Manage Projects
Key: JBIDE-22293
URL: https://issues.jboss.org/browse/JBIDE-22293
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.4.0.Alpha1
Reporter: Viacheslav Kabanovich
Assignee: Viacheslav Kabanovich
Fix For: 4.4.0.Alpha2
Open wizard Deploy Docker Image on a connection with no Projects. Fill all fields, beside OpenShift Project. Next remains disabled. Call 'Manage Projects' wizard and cancel it. Next gets incorrectly enabled.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22291) Deploy Docker Wizard: Add connection info
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22291?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich reassigned JBIDE-22291:
---------------------------------------------
Assignee: Viacheslav Kabanovich
> Deploy Docker Wizard: Add connection info
> -----------------------------------------
>
> Key: JBIDE-22291
> URL: https://issues.jboss.org/browse/JBIDE-22291
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Reporter: Marián Labuda
> Assignee: Viacheslav Kabanovich
> Labels: docker, openshift_v3
> Fix For: 4.4.0.Alpha2
>
>
> When deploying from a context menu of a docker image from Docker Explorer and an OpenShift 3 connection/project is preselected, wizard use this connection and allow to set a specific project for deployment. Problem is that I don't see a connection where I am deploying. It is nice to know that it is selected connection/project from OpenShift explorer but it would be nice to have a combo box with preselected connection there or connection info in some way to be fully aware of what I am doing.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months