[
https://issues.jboss.org/browse/JBIDE-13673?page=com.atlassian.jira.plugi...
]
Nick Boldt resolved JBIDE-13673.
--------------------------------
Resolution: Done
With the fix for JBIDE-13821 in place, and jobs updated to define job parameters for
TARGET_PLATFORM_VERSION and TARGET_PLATFORM_VERSION_MAXIMUM, we can now do this:
* -DTARGET_PLATFORM_VERSION=${TARGET_PLATFORM_VERSION} *when building* or
* -DTARGET_PLATFORM_VERSION=${TARGET_PLATFORM_VERSION_MAXIMUM} *when running tests*
I've also removed -Pmaximum from the jobs so that we're only overriding the target
platform version rather than calling an extra profile.
jenkins jobs for components and aggregates should set overrides for
TARGET_PLATFORM_VERSION and TARGET_PLATFORM_VERSION-maximum so we ensure that builds use
the correct TP regardless of their root pom's included parent pom version
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-13673
URL:
https://issues.jboss.org/browse/JBIDE-13673
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 4.1.0.Alpha1
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 4.1.0.Alpha2
jenkins jobs for components and aggregates should set overrides for
TARGET_PLATFORM_VERSION and TARGET_PLATFORM_VERSION-maximum so we ensure that builds use
the correct TP regardless of their root pom's included parent pom version
--
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