WS classpath container allows modification for source and JavaDoc locations
---------------------------------------------------------------------------
Key: JBDS-549
URL: https://jira.jboss.org/jira/browse/JBDS-549
Project: Developer Studio
Issue Type: Task
Components: Doc - JBossWS
Affects Versions: 2.0.0.beta1
Reporter: Svetlana mukhina
Assignee: Anastasiya Bogachuk
Fix For: 2.0.0.GA
WS guide should be updated according to changes made in the linked dev task.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Can't configure New Server Runtime Environment for jboss-esb-server .
---------------------------------------------------------------------
Key: JBIDE-3719
URL: https://jira.jboss.org/jira/browse/JBIDE-3719
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.0.0.GA
Environment: JBossTools-ALL-win32-3.0.0.GA-N200902020001-H1393
Reporter: Anton Klimkovich
EXECUTE: Properties-> Server -> Runtime Environments
EXECUTE: Select JBoss.org -> jboss 4.2 runtime
EXECUTE: Set path to jboss-esb-server
FAILURE: The home directory does not exist, is missing key files, or is of the incorrect version.
The same result will be if you select JBoss, a division of Red Hat group .
Think related to JBIDE-3692.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
The ESB classpath container changes description
------------------------------------------------
Key: JBDS-550
URL: https://jira.jboss.org/jira/browse/JBDS-550
Project: Developer Studio
Issue Type: Task
Components: Doc - ESB, Doc - JBossWS
Affects Versions: 2.0.0.beta1
Reporter: Svetlana mukhina
Assignee: Anastasiya Bogachuk
Fix For: 2.0.0.GA
now ESB container allows source and JavaDoc locations to be set via the Properties dialog on each contained jar. - add these to ESB guide.
check whether the same functionality was added to JBoss WS classpath container - if yes, update WS guide as well.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
RichFaces 3.3 support is implemented
-------------------------------------
Key: JBDS-556
URL: https://jira.jboss.org/jira/browse/JBDS-556
Project: Developer Studio
Issue Type: Task
Components: Doc - VisualWebTools, Doc - RHDS GSG
Affects Versions: 2.0.0.beta1
Reporter: Svetlana mukhina
Assignee: OLga Chikvina
Fix For: 2.0.0.GA
The guides must contain information about the last RF version support, make sure that link to download is up-to-date, screens of the palette are also updated.
see the linked tasks and its subtasks - all changes must be documented.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
invmTransacted not supported
----------------------------
Key: JBDS-522
URL: https://jira.jboss.org/jira/browse/JBDS-522
Project: Developer Studio
Issue Type: Bug
Affects Versions: 2.0.0.beta1
Reporter: Peter Yuill
JBDS 2.0 beta supports only .org versions for ESB Projects. The latest .org version(4.4) is not fully compatible with SOA Platform 4.3, which introduced the invmTransacted attribute in the service element of jbossesb-1.0.1.xsd . Consequently when building a service for SOA-P 4.3 (by choosing the best fit ESB 4.4) it is not possible to declare the service as invmTransacted.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
CLONE -org.jbpm.gd.jpdl has wrong provider, and wrong version?
--------------------------------------------------------------
Key: JBIDE-3716
URL: https://jira.jboss.org/jira/browse/JBIDE-3716
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jbpm
Affects Versions: 3.0.0.CR2
Reporter: Koen Aers
Assignee: Koen Aers
Fix For: 3.0.0.GA
See screenshot. This is taken from JBT 3.0.0.CR2-R200901280154.
Despite fetching from fetchTag=jbpm_jpdl_gpd_3_1_6, this shows the plugin is at 3.1.5, not 3.1.6. Is that correct? If so, then fixing the provider should increment it to 3.1.6, I suppose.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Change default workspace for rhds to a non-space version
---------------------------------------------------------
Key: RHDS-302
URL: http://jira.jboss.com/jira/browse/RHDS-302
Project: Red Hat Developer Studio
Issue Type: Feature Request
Components: Build
Affects Versions: 1.0.0.CR1
Reporter: Max Andersen
Priority: Critical
Fix For: 1.0.0.GA
Because of the issues with spaces in names for both jboss AS and hibernate annotation used in hibernate tools we should see if we could change the default from ${user.home}/workspace to ${rhdshome}/workspace
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Deleting a disconnected default jmx connection fails
----------------------------------------------------
Key: JBIDE-3710
URL: https://jira.jboss.org/jira/browse/JBIDE-3710
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jmx
Affects Versions: 3.0.0.CR2
Reporter: Rob Stryker
Assignee: Rob Stryker
Fix For: 3.0.0.GA
The delete action launches two chained jobs, disconnect -> delete. The disconnect job is not checking if it's already disconnected... causing errors.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira