[ https://issues.jboss.org/browse/JBIDE-13673?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-13673 at 3/12/13 11:37 AM: -------------------------------------------------------------- Not sure what you mean by "in the Maven executors". Anyway, I've updated the jobs in the 40x, 41x and trunk/master branches adding these to the invocation of maven. Could have added these into the MAVEN_FLAGS variable, but this is a change that happens globally anyway, not per-job, so making it harder to see in the job's configure page doesn't bother me. And not all the affected jobs use that, so this is better. :) for 40x: {code}-DTARGET_PLATFORM_VERSION=4.20.6.Final-SNAPSHOT -DTARGET_PLATFORM_VERSION-maximum=4.22.1.Final-SNAPSHOT{code} for 41x: {code}-DTARGET_PLATFORM_VERSION=4.30.5.Alpha -DTARGET_PLATFORM_VERSION-maximum=4.30.5.Alpha{code} for trunk/master: {code}-DTARGET_PLATFORM_VERSION=4.30.5.Alpha -DTARGET_PLATFORM_VERSION-maximum=4.30.5.Alpha2-SNAPSHOT{code} was (Author: nickboldt): Not sure what you mean by "in the Maven executors". Anyway, I've updated the jobs in the 40x, 41x and trunk/master branches adding these to the invocation of maven. Could have added these into the MAVEN_FLAGS variable, but this is a change that happens globally anyway, not per-job, so making it harder to see in the job's configure page doesn't bother me. And not all the affected jobs use that, so this is better. :) for 40x: {code}-DTARGET_PLATFORM_VERSION=4.20.6.Final-SNAPSHOT -DTARGET_PLATFORM_VERSION-maximum=4.22.1.Final-SNAPSHOT{code} for 41x/trunk/master: {code}-DTARGET_PLATFORM_VERSION=4.30.5.Alpha -DTARGET_PLATFORM_VERSION-maximum=4.30.5.Alpha{code} -- 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