[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

[Nick Boldt (JIRA)]

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

Nick Boldt commented on JBIDE-13673:
------------------------------------

Crap. so you mean for the test steps, we need to either:

-Pmaximum -DTARGET_PLATFORM_VERSION=[max value]

or

-Pmaximum -DTARGET_PLATFORM_VERSION-maximum=[max value]

but setting 

-Pmaximum -DTARGET_PLATFORM_VERSION=[min value] -DTARGET_PLATFORM_VERSION-maximum=[max value]

is equivalent to

-Pmaximum -DTARGET_PLATFORM_VERSION=[min value]

... sucks. :(
                
> 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