[
https://issues.jboss.org/browse/JBIDE-13821?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-13821:
---------------------------------------------
Nick - those jobs referring to it would set the flag but the flag would have *zero* effect
since the pom fixes were *not* listening to that property.
Looking in gitrepo master now seem to be sane, but 4.0.x branch still has the parent pom
where nothing will listen to -DTARGET_PLATFORM-maximum; only TARGET_PLATFORM_MAXIMUM or
tpc.version is honored.
so branch has this broken code still afaics.
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: Max Rydahl Andersen
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