-
Bug
-
Resolution: Done
-
Critical
-
4.0.x, 4.1.0.Alpha2
-
None
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.
- is related to
-
JBIDE-13452 investigate removing JBT_VERSION, JBDS_VERSION from parent pom
- Closed
-
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
- Closed
- relates to
-
JBIDE-13830 document reasons for using Eclipse Juno SR2 instead of earlier version on www.jboss.org install page for JBT 4.0.1
- Closed