[
https://issues.jboss.org/browse/JBDS-2113?page=com.atlassian.jira.plugin....
]
Nick Boldt updated JBDS-2113:
-----------------------------
Attachment: jbds-central-with-both-core-and-soa.png
Out of the box, here's how JBDS 5.0.0.Beta3's Central looks:
!jbds-central-with-both-core-and-soa.png!
(from jbdevstudio-product-universal-5.0.0.v201205020209N-H1255-CR1.jar)
relabel categories / connectors in Central and Update sites
-----------------------------------------------------------
Key: JBDS-2113
URL:
https://issues.jboss.org/browse/JBDS-2113
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: central, SOA Tooling / Platform , updatesite
Affects Versions: 5.0.0.Beta1-SOA
Reporter: Nick Boldt
Assignee: Douglas Palmer
Attachments: jbds-central-with-both-core-and-soa.png
Latest suggestions for how to fix JBDS SOA Central [1] and JBDS SOA Update Sites [2]:
* [JBDS Updates] relabel "BRMS Tooling" category to "Business Rules
Tooling" (to match Central)
* [JBDS Central] relabel "BRMS Tooling" category to "Business Rules
Tooling" (to match update site)
* [JBDS Updates] relabel "SOA-P Tooling" category to "SOA and Data
Services Tooling" (to match Central)
* [JBDS Central] relabel "SOA-P Tooling" category to "SOA and Data
Services Tooling" (to match update site)
* [JBDS Updates] move Modeshape into JBoss Data Services and also include in "SOA
and Data Services Tooling" category (to match Central)
* [JBDS Central] add jbpm5 to SOA and Data Services Tooling" category
[1]
https://issues.jboss.org/secure/attachment/12353521/12353521_jbds5-jbds-s...
[2]
https://issues.jboss.org/secure/attachment/12353655/JBDS2078.snap.png,
http://www.qa.jboss.com/binaries/RHDS/builds/staging/soatools-5.0.0.Beta1...
Note too that there is also the JBT SOA Central [3] and JBT SOA Update Site [4]:
[3]
https://issues.jboss.org/secure/attachment/12353522/12353522_eclipse37jee...,
[4]
http://download.jboss.org/jbosstools/builds/staging/soatools-3.3.0.Beta1-...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira