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

[Mickael Istria (JIRA)]

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

Mickael Istria commented on JBIDE-12761:
----------------------------------------

{quote}
 [Mickael] 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
{quote}

This is already done by those jobs:
* https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Trunk/job/jbosstools-4.0_trunk.install-tests-e4.2-jbt_trunk/
* https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Trunk/job/jbosstools-4.0_trunk.install-tests-eclipseLatest-jbt_trunk/
                
> 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: Mickael Istria
>             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