|
If you were logged in you would be able to see more operations.
|
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
JEEAS-185 is fixed, but the following minor defect is observed. (It may be generic, but observed for Glassfish configurations.)
Get 2 local Glassfish configurations. Make their debugger port numbers the same and matching Glassfish installation. So, there is no error message.
1. Open Run configuration dialog, expand the list of Glassfish configurations.
2. Now change the port for configuration A. It becomes "red" (erroneous), quick fix is suggested.
3. Apply the fix. Press Apply in dialog. The port is changed in Glassfish installation. A still looks "red" in tree view. (Problem 1.)
4. Select A in the tree view. It changes the view to "ok".
5. The appearance of B in the tree view is still "ok". (Problem 2.)
6. Select B. Ok to close dialog. B becomes current, and now shown "red" in main toolbar.
7. Reopen run configurations dialog. The fix is applied to B and it turns to "ok".
So, there are the problems with updating "ok" / "error" status in tree view on quick fix.
|
|
Description
|
JEEAS-185 is fixed, but the following minor defect is observed. (It may be generic, but observed for Glassfish configurations.)
Get 2 local Glassfish configurations. Make their debugger port numbers the same and matching Glassfish installation. So, there is no error message.
1. Open Run configuration dialog, expand the list of Glassfish configurations.
2. Now change the port for configuration A. It becomes "red" (erroneous), quick fix is suggested.
3. Apply the fix. Press Apply in dialog. The port is changed in Glassfish installation. A still looks "red" in tree view. (Problem 1.)
4. Select A in the tree view. It changes the view to "ok".
5. The appearance of B in the tree view is still "ok". (Problem 2.)
6. Select B. Ok to close dialog. B becomes current, and now shown "red" in main toolbar.
7. Reopen run configurations dialog. The fix is applied to B and it turns to "ok".
So, there are the problems with updating "ok" / "error" status in tree view on quick fix. |
Show » |
|
Usability Problem
Open
Normal
After applying a quick fix in one run configuration, the other's appearance is not updated immediately
1.) Create a web facet which builds a 'web.war' file;
2.) Create a Tomcat run configuration and select the 'web.war' deployment source;
3.) Make a copy of this Tomcat run configuration;
4.) Choose 'Configure...' in the deployment source editor;
5.) Modify the web facet that no war file is created;
6.) The current Tomcat run configuration is marked as invalid;
7.) Select the other Tomcat run configuration -> only now it is marked as invalid too.