[jbosstools-issues] [JBoss JIRA] (JBIDE-12761) Target-platfom should contain "minimal compatible" version of dependencies

[ https://issues.jboss.org/browse/JBIDE-12761?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-12761 at 10/11/12 5:32 PM: -------------------------------------------------------------- Per decisions made in http://ether-man.rhcloud.com/p/build.next on Oct 10, the target platform used for building all of JBT should now be the latest minimum one (currently SR0b) rather than the latest maximum (currently SR1): {quote} JBT - set up component jobs to do this: * [Nick] create profiles for "minimum" (enabled by default, unified.target) and new "maximum" target :: *DONE* * [Nick] update jobs to do this: * mvn clean install -DskipTests -Pminimum.target (or equivalent) # build :: *DONE* * publish.sh # publish :: *DONE* * mvn verify -f tests/pom.xml -P*maximum* (or equivalent) # test :: *DONE* JBT aggregate build with latest TP mirror - http://download.jboss.org/jbosstools/updates/juno/SR1/ * point at latest TP mirror via http://anonsvn.jboss.org/repos/jbosstools/trunk/build/aggregate/site/asso... * this means the installation and the backing TP site contain the same bits -- latest Juno reqs * [Nick] to verify this is correct in both trunk/branch & release_guide docs Installation tests (fired downstream from JBT build) * 0. fetch Eclipse * 1. install JBT from update site into 4.2, 4.2.latest * 2. install JBT Central features into 4.2, 4.2.latest JBDS - single job for sites + installer (as we do today) * build Product and Extras update sites w/ latest TP [trunk AND branch] * build installers w/ latest TP [trunk AND branch] * build composite sites using latest TP -- https://devstudio.jboss.com/updates/6.0-staging/compositeContent.xml - point to Core site (built with latest TP) and latest TP mirror on devstudio.jboss.com * this means the installer and the backing update site contain the same bits -- latest Juno reqs * [Nick] verify the above is true/working {quote} was (Author: nickboldt): Per decisions made in http://ether-man.rhcloud.com/p/build.next on Oct 10, the target platform used for building all of JBT should now be the latest minimum one (currently SR0b) rather than the latest maximum (currently SR1): {quote} JBT - set up component jobs to do this: * [Mistria] create profiles for "minimum" and "maximum" targets * [Mistria] update jobs to do this: * mvn clean install -DskipTests -Pminimum.target (or equivalent) # build * publish.sh # publish * mvn verify -f tests/pom.xml -Platest.target (or equivalent) # test JBT aggregate build with latest TP mirror - http://download.jboss.org/jbosstools/updates/juno/SR1/ * point at latest TP mirror via http://anonsvn.jboss.org/repos/jbosstools/trunk/build/aggregate/site/asso... * this means the installation and the backing TP site contain the same bits -- latest Juno reqs * [Nick] to verify this is correct in both trunk/branch & release_guide docs Installation tests (fired downstream from JBT build) * 0. fetch Eclipse * 1. install JBT from update site into 4.2, 4.2.latest * 2. install JBT Central features into 4.2, 4.2.latest JBDS - single job for sites + installer (as we do today) * build Product and Extras update sites w/ latest TP [trunk AND branch] * build installers w/ latest TP [trunk AND branch] * build composite sites using latest TP -- https://devstudio.jboss.com/updates/6.0-staging/compositeContent.xml - point to Core site (built with latest TP) and latest TP mirror on devstudio.jboss.com * this means the installer and the backing update site contain the same bits -- latest Juno reqs * [Nick] verify the above is true/working {quote} -- 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