[jbosstools-issues] [JBoss JIRA] (JBIDE-13673) 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
[
https://issues.jboss.org/browse/JBIDE-13673?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-13673:
----------------------------------------
Need max value for tests. Because at some point min won't be the
same as max, and we test w/ max while building w/ min.
Right
But setting the -DTARGET_PLATFORM_VERSION value simply overrides any other setting of
target platform (such as profile or TARGET_PLATFORM_VERSION-maximum. What about removing
the minimal and maximal profiles from CI jobs and set TARGET_PLATFORM_VERSION with
different values (minimal and maximal) in the Maven executors?
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