[JBoss JIRA] Created: (JBDS-1627) 3rd party certification for JBDS 5.x
by Nick Boldt (JIRA)
3rd party certification for JBDS 5.x
------------------------------------
Key: JBDS-1627
URL: https://issues.jboss.org/browse/JBDS-1627
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Components: 3rdPartyCertification, 3rdPartyDependencies, Requirements
Reporter: Max Rydahl Andersen
Priority: Blocker
Fix For: 4.x
We should define what kind of certifications we want and then certify 3rd party plugins with JBDS
Certifiaction could for example be for Groovy Plugin we know it installs, but beyond that there aren't any guarantees.
For m2eclipse it would be the same with respect to installation but that we support the maven integration plugins and provide fixes for that - but not m2eclipse it self.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months
[JBoss JIRA] Created: (JBIDE-6579) [tester] UI suggestion for WS Tester
by Max Rydahl Andersen (JIRA)
[tester] UI suggestion for WS Tester
------------------------------------
Key: JBIDE-6579
URL: https://jira.jboss.org/browse/JBIDE-6579
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Webservices
Reporter: Max Rydahl Andersen
Assignee: Brian Fitzpatrick
Tried out the ws tester today and been thinking about better layout since it is rather bulky today
I'll attach a mockup of it but in "short" its:
1) Reduce redundant text (i.e. XXX instead of Request XXX)
2) Make input field directly visible (less tabs)
3) Avoid text buttons where icons can be used
4) Remove duplicate functionallity (tcp monitor does not seem to provide functionallity outside of what tcp monitor does)
5) Let the output be Save, open in editor based on content type, show "raw" and show in "embedded browser"
6) Tab and save input between sessions to avoid retyping.
7) Consider add history back/forward buttons ?
--
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
13 years, 10 months
[JBoss JIRA] Created: (JBIDE-8791) JBoss 6 and 7 not found
by Rob Stryker (JIRA)
JBoss 6 and 7 not found
------------------------
Key: JBIDE-8791
URL: https://issues.jboss.org/browse/JBIDE-8791
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 3.3.0.M1
Reporter: Rob Stryker
Assignee: Nick Boldt
Priority: Critical
Fix For: 3.3.0.M1
https://hudson.qa.jboss.com/hudson/view/DevStudio_Trunk/job/jbosstools-3....
Only two tests showing failing in this build are:
* org.jboss.ide.eclipse.as.test.ASTestSuite.testAS60Exists
* org.jboss.ide.eclipse.as.test.ASTestSuite.testAS70Exists
These tests are simple and just verify the passed-in folders / locations actually exist on the host machine. They don't even really do anything else, no verification of whether its a proper server or not. Just, does the folder exist.
If you dont have time to fix / check it out, tell me and i'll comment out those two tests...
It seems only yesterday we were setting fire to Strong Sad's underdrawers. (that *WAS* yesterday!)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months
[JBoss JIRA] Created: (JBIDE-8425) add capability to chain jobs so that successor jobs dont get executed if predecessors are canceled / fail
by Andre Dietisheim (JIRA)
add capability to chain jobs so that successor jobs dont get executed if predecessors are canceled / fail
---------------------------------------------------------------------------------------------------------
Key: JBIDE-8425
URL: https://issues.jboss.org/browse/JBIDE-8425
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: deltacloud
Affects Versions: 3.2.0.CR1
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Priority: Minor
Fix For: 3.3.x
The current implementation of ChainedJob chains jobs so that all of them are executed regardless if the predecessors are canceled or fail.
In the context of deltacloud there's no need to create an RSE (successor job) if launching the instance (predecessor job) was canceled/failed. There's no way for the RSE creation job to know if the launch was canceled/failed. It may only guess so if the instance is null or has no hostname.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months