[jbosstools-issues] [JBoss JIRA] (JBDS-2251) reorder qualifiers on update site pages to match the new sequence in parent pom (${BUILD_ALIAS}-v${timsetamp}-H${JOB_NUMBER} instead of v${timsetamp}-H${JOB_NUMBER}-${BUILD_ALIAS})

[Nick Boldt (JIRA)]

Nick Boldt created JBDS-2251:
--------------------------------

             Summary: reorder qualifiers on update site pages to match the new sequence in parent pom (${BUILD_ALIAS}-v${timsetamp}-H${JOB_NUMBER} instead of v${timsetamp}-H${JOB_NUMBER}-${BUILD_ALIAS})
                 Key: JBDS-2251
                 URL: https://issues.jboss.org/browse/JBDS-2251
             Project: Developer Studio (JBoss Developer Studio)
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Build, updatesite
    Affects Versions: 6.0.0.M1
            Reporter: Nick Boldt
            Assignee: Nick Boldt
             Fix For: 6.0.0.M1


Denis started us down the path toward having qualifiers for features/plugins starting with M1 or Beta2 instead of a timestamp, because Max prefers that.

However, more work is needed to ensure we consistently implement the same scheme everywhere, including pages such as these:

http://download.jboss.org/jbosstools/updates/nightly/core/trunk/
http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-6.0_trunk.updatesite/extras/
http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-6.0_trunk.updatesite/all/

We could also consider using "J" instead of "H" for the build # since we now run Jenkins instead of Hudson. Or else a "B" for Build Number.


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