[jbosstools-issues] [JBoss JIRA] (JBIDE-13821) CI runs tests against minimum instead of maximum
Nick Boldt (JIRA)
jira-events at lists.jboss.org
Mon Mar 25 19:57:42 EDT 2013
[ https://issues.jboss.org/browse/JBIDE-13821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12763074#comment-12763074 ]
Nick Boldt edited comment on JBIDE-13821 at 3/25/13 7:56 PM:
-------------------------------------------------------------
The 4.0.x jobs were updated to use
{code} clean install ${MAVEN_FLAGS} -gs /home/hudson/.m2/settings.xml -s ${WORKSPACE}/settings/hudson-settings.xml
-DTARGET_PLATFORM_VERSION=4.20.6.Final-SNAPSHOT -DTARGET_PLATFORM_VERSION_MAXIMUM=4.22.2.Final-SNAPSHOT {code}
instead of
{code} clean install ${MAVEN_FLAGS} -gs /home/hudson/.m2/settings.xml -s ${WORKSPACE}/settings/hudson-settings.xml
-DTARGET_PLATFORM_VERSION=4.20.6.Final-SNAPSHOT -DTARGET_PLATFORM_VERSION-maximum=4.22.2.Final-SNAPSHOT {code}
so there are no longer any references to the old variable, which means this issue can be closed.
was (Author: nickboldt):
4.0.x jobs were updated to use clean install ${MAVEN_FLAGS} -gs /home/hudson/.m2/settings.xml -s ${WORKSPACE}/settings/hudson-settings.xml -DTARGET_PLATFORM_VERSION=4.20.6.Final-SNAPSHOT -DTARGET_PLATFORM_VERSION_MAXIMUM=4.22.2.Final-SNAPSHOT
instead of
clean install ${MAVEN_FLAGS} -gs /home/hudson/.m2/settings.xml -s ${WORKSPACE}/settings/hudson-settings.xml -DTARGET_PLATFORM_VERSION=4.20.6.Final-SNAPSHOT -DTARGET_PLATFORM_VERSION-maximum=4.22.2.Final-SNAPSHOT
so...
nothing to do here.
/me takes a deep breath
Closing.
> CI runs tests against minimum instead of maximum
> ------------------------------------------------
>
> Key: JBIDE-13821
> URL: https://issues.jboss.org/browse/JBIDE-13821
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng
> Affects Versions: 4.0.x, 4.1.0.Alpha2
> Reporter: Mickael Istria
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 4.0.1.Final, 4.1.0.Alpha2
>
>
> As Maven executions set a value for the TARGET_PLATFORM_VERSION value, this property is not overriden by the maximum profile.
> Maven order to set properties is
> # look a -D... to set property, if not found
> # look at active profiles to set property, if not found
> # look at default value of property to set it
> This makes that in mvn execution for tests, the TARGET_PLATFORM_VERSION is set to minimal is CI jobs, whereas with using the -Pmaximun profile, we expect maximum.
> This is a critical issue since it caused hours of confusions to debug on 4.0.x branch.
--
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
More information about the jbosstools-issues
mailing list