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

[Nick Boldt (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-12761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12725706#comment-12725706 ] 

Nick Boldt edited comment on JBIDE-12761 at 10/11/12 5:33 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/associate.properties
*    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:
*    [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/associate.properties
*    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}
                  
> Target-platfom should contain "minimal compatible" version of dependencies
> --------------------------------------------------------------------------
>
>                 Key: JBIDE-12761
>                 URL: https://issues.jboss.org/browse/JBIDE-12761
>             Project: Tools (JBoss Tools)
>          Issue Type: Enhancement
>          Components: target-platform
>            Reporter: Mickael Istria
>            Assignee: Nick Boldt
>             Fix For: 4.0.0.Beta1
>
>
> Currently, TP contains the latest version of all dependencies. However, JBT can run on lower versions of Eclipse. It happens that developer introduce a depdendency on a very recent version when it's not necessary because they rely on our target-platform.
> Instead, TP should contain the minimal versions of all dependencies that are compatible with JBoss Tools. Then developers can rely on very old version, and when necessary, request usage of new one and break dependencies.
> Installation tests are already there to verify installation on latest versions of Eclipse.

--
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