[JBoss JIRA] Created: (JBIDE-6652) Implement ModeShape capability/activity to enable/disable ModeShape functionality
by Brian Fitzpatrick (JIRA)
Implement ModeShape capability/activity to enable/disable ModeShape functionality
---------------------------------------------------------------------------------
Key: JBIDE-6652
URL: https://jira.jboss.org/browse/JBIDE-6652
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: modeshape
Affects Versions: 3.2.0.M1
Reporter: Brian Fitzpatrick
Assignee: Dan Florian
Fix For: 3.2.x
As we discussed on the phone, the use of Capabilities/Activities in Eclipse might be a good way to handle the "Always On" aspect of the ModeShape menus in JBoss Tools. For some reason, this functionality is labeled as "Capabilities" in Eclipse Preferences, but the actual extension point is "org.eclipse.ui.activities" and called Activities in the API documentation. Go figure.
That said, it's very simple to implement. I'll attach a patch with the suggested tweaks to plugin.xml and plugin.properties. But this should address Max's issues with the ModeShape menus appearing on all folders and files and be easy to add to the documentation.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 5 months
[JBoss JIRA] Created: (JBIDE-7518) Cloud View: need to refresh cloud after correcting url
by Andre Dietisheim (JIRA)
Cloud View: need to refresh cloud after correcting url
------------------------------------------------------
Key: JBIDE-7518
URL: https://jira.jboss.org/browse/JBIDE-7518
Project: Tools (JBoss Tools)
Issue Type: Bug
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
how to reproduce:
1) create a new connection and use an invalid url
2) cloud viewer: the connection has no instances, nor images
3) select "edit connection" in the cotext menu
4) correct the url, enter a valid one this time
5) hit finish and go back to the instances and images in your connection
Result:
The connection has no images nor instances. If you refresh the connection (hit F5), you'll get the instance and images
Expected:
The connection immediately shows instances and images after editing it. No refresh shall be necessary.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 5 months
[JBoss JIRA] Created: (JBIDE-7407) Regression testing connection in Deltacloud New Cloud Connection dialog
by Jeff Johnston (JIRA)
Regression testing connection in Deltacloud New Cloud Connection dialog
-----------------------------------------------------------------------
Key: JBIDE-7407
URL: https://jira.jboss.org/browse/JBIDE-7407
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 3.2.0.Beta1
Reporter: Jeff Johnston
Assignee: Andre Dietisheim
Fix For: 3.2.0.Beta2
When creating a cloud connection, one is able to test the connection (i.e. that the username and password are valid) via pushing the Test button. If a bad username and password is entered, the dialog will respond that the test failed. This no longer works in that all combinations report success..
I have traced the problem to the removal of the DeltaCloudAuthException being thrown in the DeltaCloudClient code when the status code is 403 (forbidden). The DeltaCloud method testConnection() is waiting for this exception and either it should be thrown or some other code is needed to replace it. to determine that authorization has failed.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 5 months