-
Bug
-
Resolution: Done
-
Major
-
4.1.0.Alpha1
-
None
investigate removing JBT_VERSION, JBDS_VERSION, and TARGET_PLATFORM_VERSION (min and max) from parent pom
Can we switch to using dynamic maven variables like project.version instead?
Moving forward, jobs will override/set the version of target platform used to build (min) and test (max), and developers will be required to decide when/if to move to a newer parent pom or target platform version(s) if needed. For projects that are released, jobs will run only when TP changes (ie., will watch the jbosstools-target-platforms repo for changes).
- relates to
-
JBIDE-13821 CI runs tests against minimum instead of maximum
- Closed
-
JBDS-2466 Links to target platform on JBDS builds download page are not valid and page is mentioning Eclipse Juno instead of Eclipse Kepler as TP
- 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
-
JBIDE-18820 define how to handle ide.properties and avoid parent pom to always change
- Closed
-
JBIDE-18806 When discovery URL is not set, "Software/Updates" page is silently hidden
- Closed