[
https://issues.jboss.org/browse/JBIDE-13452?page=com.atlassian.jira.plugi...
]
Nick Boldt edited comment on JBIDE-13452 at 3/18/13 6:00 PM:
-------------------------------------------------------------
BTW, as much as I hate to admit it, TARGET_PLATFORM_VERSION-maximum was a terrible name
choice - it doesn't work as expected w/ shell and ant scripts. Can we look at changing
that to TARGET_PLATFORM_VERSION_MAXIMUM or something better? Did [~maxandersen]'s
patch for tpc.version ever get applied?
was (Author: nickboldt):
BTW, as much as I hate to admit it, TARGET_PLATFORM_VERSION-maximum was a terrible
name choice. Can we look at changing that to TARGET_PLATFORM_VERSION_MAXIMUM or something
else? Did [~maxandersen]'s patch for tpc.version ever get applied?
investigate removing JBT_VERSION, JBDS_VERSION, and
TARGET_PLATFORM_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