[ https://issues.jboss.org/browse/JBIDE-26673?page=com.atlassian.jira.plugi... ] André Dietisheim commented on JBIDE-26673: ------------------------------------------ [~msparrao] thx for updating us. Like @robstryker I see no hard requirement on rse versions in our plugins afaics. We have org.jboss.ide.eclipse.as.rse.core requiring a non-specified version of org.eclipse.rse.core: {code:title=https://github.com/jbosstools/jbosstools-server/blob/master/as/plugins/org.jboss.ide.eclipse.as.rse.core/META-INF/MANIFEST.MF#L12} Bundle-SymbolicName: org.jboss.ide.eclipse.as.rse.core;singleton:=true Bundle-Version: 3.7.0.qualifier Require-Bundle: ... org.eclipse.rse.core, org.eclipse.rse.subsystems.files.core, org.eclipse.rse.services, org.eclipse.rse.services.files.ftp, org.eclipse.rse.services.local, org.eclipse.rse.services.ssh, org.eclipse.rse.subsystems.shells.core, ... {code} The problem I see is that rse version >= 4.0.0 is expected to break API compatibilty (see https://wiki.eclipse.org/Version_Numbering#When_to_change_the_minor_segment). Anpther thing that bothers me is that according to [~nickboldt] there is no publicly available rse v4.6, so there's no way for us currently to test/verify this newer rse plugin. You seem to imply that there's a closed source version 4.6 available from IBM? What's the plugin that you're using that requires 4.6? -- This message was sent by Atlassian Jira (v7.12.1#712002)