[jbosstools-issues] [JBoss JIRA] (JBIDE-16902) Widen dependency range from org.jboss.tools.as.core to org.eclipse.core.resources

[Mickael Istria (JIRA)]

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

Mickael Istria commented on JBIDE-16902:
----------------------------------------

Ok. That's somehow strange because platform use semantic versioning so increasing the minor segment should affect consumers of the API.
Do you recall the API change that made that necessary on Server?
                
> Widen dependency range from org.jboss.tools.as.core to org.eclipse.core.resources
> ---------------------------------------------------------------------------------
>
>                 Key: JBIDE-16902
>                 URL: https://issues.jboss.org/browse/JBIDE-16902
>             Project: Tools (JBoss Tools)
>          Issue Type: Enhancement
>          Components: server
>    Affects Versions: 4.1.2.Final
>            Reporter: Mickael Istria
>            Assignee: Rob Stryker
>
> In 4.1.2.Final, bundle org.jboss.ide.eclipse.as.core has a dependency on org.eclipse.core.runtime [3.7,3.10). Is such a narrow dependency range intentional? Is there anything in 3.10 and later that prevent this bundle from working well?
> If not, then it's a pity, because it makes that just by setting up a maxVersion, JBoss Tools 4.1.2 cannot be installed in Luna M6, without providing additional value. In general, unless some actual issues are noticed, maxVersions are to be avoided or set to the next major (eg [3.7,4.0) ) for best compatibility. 

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