[jbosstools-issues] [JBoss JIRA] (JBIDE-13452) investigate removing JBT_VERSION, JBDS_VERSION from parent pom

[Nick Boldt (JIRA)]

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

Nick Boldt commented on JBIDE-13452:
------------------------------------

* *TARGET_PLATFORM_VERSION-maximum* removed from job configs in DevStudio_Trunk and DevStudio_7.0.kepler view, in favour of *TARGET_PLATFORM_VERSION_MAXIMUM*.
* *TARGET_PLATFORM_VERSION-maximum* removed from aggregate/site/pom.xml and aggregate/webtools-site/pom.xml, in favour of *TARGET_PLATFORM_VERSION_MAXIMUM*.
                
> investigate removing JBT_VERSION, JBDS_VERSION from parent pom
> --------------------------------------------------------------
>
>                 Key: JBIDE-13452
>                 URL: https://issues.jboss.org/browse/JBIDE-13452
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: Build/Releng, target-platform, updatesite
>    Affects Versions: 4.1.0.Alpha1
>            Reporter: Nick Boldt
>            Assignee: Nick Boldt
>
> investigate removing JBT_VERSION, JBDS_VERSION, and TARGET_PLATFORM_VERSION (min and max) from parent pom
> Can we switch to using dynamic maven variables like project.version instead?
> Moving forward, jobs will override/set the version of target platform used to build (min) and test (max), and developers will be required to decide when/if to move to a newer parent pom or target platform version(s) if needed. For projects that are released, jobs will run only when TP changes (ie., will watch the jbosstools-target-platforms repo for changes).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira