[JBoss JIRA] (JBIDE-23602) Server adapter: Hot code replace failed dialog has poor usability
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-23602:
----------------------------------------
Summary: Server adapter: Hot code replace failed dialog has poor usability
Key: JBIDE-23602
URL: https://issues.jboss.org/browse/JBIDE-23602
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Affects Versions: 4.4.2.Final
Reporter: Andre Dietisheim
Fix For: 4.4.3.AM1
steps to reproduce:
# ASSERT: have jboss-helloworld running in OpenShift (create it via eap64-basic-s2i template), the source code for it imported to a workspace project and a server adapter for it
# EXEC: open HelloService and change it to the following:
{code:title=HelloService}
public class HelloService {
private static final String MAGIC_STRING = "42";
String createHelloMessage(String name) {
return "Hello " + name + ", the magic string is " + MAGIC_STRING + "!";
}
}
{code}
and save the editor
Result:
"Hot code replace failed" dialog pops up, which is expected.
!hot-code-replace-failed-2.png!
But it's usability is poor:
* the affected module is not fully shown (half of it cut off)
* there's no margin on the right border of the dialog
* No button is pre-selected so that I can simply hit Return to pick a sane default choice (I have to hit tap to get to the button I want to press or use my mouse).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBIDE-23567) Integration tests global refactoring
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23567?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-23567:
-------------------------------
Sprint: devex #124 December 2017
> Integration tests global refactoring
> ------------------------------------
>
> Key: JBIDE-23567
> URL: https://issues.jboss.org/browse/JBIDE-23567
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: integration-tests
> Reporter: Jeff MAURY
> Labels: integration-test, integration_tests
> Fix For: 4.4.3.AM1
>
>
> We should done some work on integration tests so that we can rely on them to improve our code quality and reduce the technical debt.
> A sprint will be dedicated.
> Here are the tasks we should work on:
> * run tests from Maven and document how to run them if specific steps are required
> * If failure, fix the failed tests
> * Refactor / move tests to the components repository
> * Fix/make sure tests are run in PR check
> This huge task should be done component per component. Sub-tasks JIRA will be created for each component.
> You can use this document as a starting point:[https://docs.google.com/document/d/1bl8pJ2aW65UpyGpr3qxoAUREDWL26N...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month