[jbosstools-issues] [JBoss JIRA] (JBDS-2212) audit version numbers of features/plugins in JBDS 5.0.0 vs. 4.1.3

[Nick Boldt (JIRA)]

    [ https://issues.jboss.org/browse/JBDS-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12704483#comment-12704483 ] 

Nick Boldt commented on JBDS-2212:
----------------------------------

Respining to pick up fixed versions in 33x:

https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_stable_branch.component--central/ >=104
https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_stable_branch.component--common >=77
https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_stable_branch.component--jst >=87
https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_stable_branch.component--maven >=120
https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_stable_branch.component--openshift >=138
https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_stable_branch.component--portlet >=95
https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_stable_branch.component--examples >=111
https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_stable_branch.component--ws >=138

https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_stable_branch.aggregate/ >=195

                
> audit version numbers of features/plugins in JBDS 5.0.0 vs. 4.1.3
> -----------------------------------------------------------------
>
>                 Key: JBDS-2212
>                 URL: https://issues.jboss.org/browse/JBDS-2212
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Build, updatesite
>    Affects Versions: 5.0.0.GA
>            Reporter: Nick Boldt
>            Assignee: Nick Boldt
>             Fix For: 5.0.1.GA
>
>         Attachments: 412vs500-feature-plugin-versions0.png, 412vs500-feature-plugin-versions1.png, 412vs500-feature-plugin-versions2.png, 412vs500-feature-plugin-versions3.png, 412vs500-feature-plugin-versions4.png, 412vs500-feature-versions.png, JBDS2212-central-upversion-33x.patch, JBDS2212-common-upversion-33x.patch, JBDS2212-examples-upversion-33x.patch, JBDS2212-jst-upversion-33x.patch, JBDS2212-maven-upversion-33x.patch, JBDS2212-openshift-upversion-33x.patch, JBDS2212-portlet-upversion-33x.patch, JBDS2212-ws-upversion-33x.patch
>
>
> Should have done this a while ago, but incorrectly assumed component leads were taking ownership of their versioning as they are the SMEs for their content and API changes.
> Hibernate should definitely be incremented since it's at version 3.4.1 in JBDS 4.1.3, but only 3.4.0 in 5.0.0.
> !412vs500-feature-versions.png!
> !412vs500-feature-plugin-versions4.png!
> {code}
> org_hibernate_eclipse=3.4.0
> org_hibernate_eclipse_console=3.4.0
> org_hibernate_eclipse_feature=3.4.0
> org_hibernate_eclipse_help=3.4.0
> org_hibernate_eclipse_jdt_apt_ui=3.4.0
> org_hibernate_eclipse_jdt_ui=3.4.0
> org_hibernate_eclipse_libs=3.4.0
> org_hibernate_eclipse_mapper=3.4.0
> {code}
> Based on screenshots above, should these be upversioned?
> !412vs500-feature-plugin-versions3.png!
> {code}
> org_jboss_ide_eclipse_archives_core=3.2.1
> org_jboss_ide_eclipse_archives_feature=3.2.1
> org_jboss_ide_eclipse_archives_jdt_integration=3.2.1
> org_jboss_ide_eclipse_archives_ui=3.2.1
> {code}
> !412vs500-feature-plugin-versions2.png!
> {code}
> org_jboss_tools_jmx_core=1.2.0
> org_jboss_tools_jmx_feature=1.2.0
> org_jboss_tools_jmx_ui=1.2.0
> {code}
> !412vs500-feature-plugin-versions1.png!
> {code}
> org_jboss_tools_portlet_core=1.2.0
> org_jboss_tools_portlet_feature=1.2.0
> org_jboss_tools_portlet_ui=1.2.0
> {code}
> !412vs500-feature-plugin-versions0.png!
> {code}
> org_jboss_tools_ws_core=1.2.2
> org_jboss_tools_ws_creation_core=1.2.2
> org_jboss_tools_ws_creation_ui=1.2.2
> org_jboss_tools_ws_feature=1.2.2
> org_jboss_tools_ws_jaxrs_core=1.2.2
> org_jboss_tools_ws_jaxrs_feature=1.2.2
> org_jboss_tools_ws_jaxrs_ui=1.2.2
> org_jboss_tools_ws_ui=1.2.2
> {code}

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