[
https://issues.jboss.org/browse/JBIDE-13452?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-13452:
------------------------------------
Still to do:
* Remove JBT_VERSION from parent/pom.xml (master only)
* Remove TARGET_PLATFORM_VERSION-maximum from parent/pom.xml (master only, see
JBIDE-13821)
* Determine if JBDS_VERSION can be replaced with ${project.version} in these files:
{code}
./product/pom.xml
./product/installer/build.xml
./product/installer/pom.xml
./product/results/build.xml
./product/results/index-earlyaccess-template.html
./product/results/index-internal-template.html
./product/results/index-local-template.html
./product/results/pom.xml
./product/site/build.xml
./product/site/pom.xml
./product-soa/site/build.xml
./product-soa/site/pom.xml
{code}
./product/sources/build.xml
./product/sources/pom.xml
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