[jbosstools-issues] [JBoss JIRA] Created: (JBDS-1836) Relabel "Certified" features as "Selected" to match the actual level of support provided for those add-ons in 4.x

[Nick Boldt (JIRA)]

Relabel "Certified" features as "Selected" to match the actual level of support provided for those add-ons in 4.x
-----------------------------------------------------------------------------------------------------------------

                 Key: JBDS-1836
                 URL: https://issues.jboss.org/browse/JBDS-1836
             Project: Developer Studio (JBoss Developer Studio)
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: 3rdPartyCertification, 3rdPartyDependencies, documentation, updatesite
    Affects Versions: 4.1.1.M1, 5.0.0.M3
            Reporter: Nick Boldt
            Assignee: Nick Boldt
             Fix For: 4.1.1.Final, 5.0.0.M4


Per lengthy discussions, I believe the plan is to relabel some features on the JBDS Extras sites for *BOTH 4.x and 5.x* as follows:

{code}
* Selected *
    FindBugs
    Git (5.x version includes eGit, jGit, and Mylyn support for GitHub; 4.x version is just eGit/jGit)
    Maven/m2e (including wtp integration)
    Mylyn (incl. connectors for CVS, SVN, Git, GitHub; JIRA support only in 5.x)
    PMD
    Subclipse
    jslint (new for JBDS 5.x)
    checkstyle (new for JBDS 5.x)

* Certified *
    Spring IDE (per Burr)
    BPEL Editor (per Mike)
    TestNG (per Max)
{code}

To facilitate with this exercise, I've changed the update site index pages to list the features they contain. Here are the latest nightlies for 4.x and 5.x:

http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-4.1_stable_branch.updatesite/extras/
  and 
http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-5.0_trunk.updatesite/extras/
http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-5.0_trunk.soa-tooling.updatesite/product-soa/ (not technically an "Extras" site but listed here in case people wonder where BPEL went)


--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira