[jbosstools-issues] [JBoss JIRA] (JBDS-2113) relabel categories / connectors in Central and Update sites

[Nick Boldt (JIRA)]

     [ https://issues.jboss.org/browse/JBDS-2113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nick Boldt updated JBDS-2113:
-----------------------------

    Attachment: jbds-central-beta3-with-soa-beta2.png


Using this hacked-up devstudio-directory.xml:

{code}
<?xml version='1.0' encoding='UTF-8'?>
<directory xmlns="http://www.eclipse.org/mylyn/discovery/directory/">
<!-- include JBDS Core Central discovery plugin -->
<entry url="discovery/com.jboss.jbds.central.discovery_1.0.0.v20120514-2058-H159-Beta3.jar" permitCategories="true"/>
<!-- include JBDS SOA Central discovery plugin too -->
<entry url="http://www.qa.jboss.com/binaries/RHDS/updates/development/5.0.0.Beta2.soa-tooling/plugins/com.jboss.jbds.central.discovery.soa-tooling_1.0.0.v20120522-2301-H13-Beta2-SOA.jar" permitCategories="true"/>
</directory>
{code}

Which I'm self-hosting as http://localhost:8080/devstudio.jboss.com/updates/5.0/staging/devstudio-directory.xml

I can run JBDS like this:

{code}
$ ./jbdevstudio -vmargs -Djboss.discovery.directory.url=http://localhost:8080/devstudio.jboss.com/updates/5.0/staging/devstudio-directory.xml
{code}

And the result is this:

!jbds-central-beta3-with-soa-beta2.png!
                
> 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: Nick Boldt
>             Fix For: 5.0.0.Beta2-SOA
>
>         Attachments: jbds-central-beta3-with-soa-beta2.png, 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)
> [1] https://issues.jboss.org/secure/attachment/12353521/12353521_jbds5-jbds-soa-tooling-site.png
> [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--JBDS-updatesite/product-soa/
> 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-jbosstools-soa-tooling-site.png, 
> [4] http://download.jboss.org/jbosstools/builds/staging/soatools-3.3.0.Beta1--aggregate/all/repo/

--
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