[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-3873) JBoss AS and Server view not avaiable

[ https://jira.jboss.org/jira/browse/JBIDE-3873?page=com.atlassian.jira.plu... ] John Graham commented on JBIDE-3873: ------------------------------------ The problem here is that org.jboss.ide.eclipse.as.ui now has a minimum version prerequisite on org.eclipse.jst.j2ee.core=1.1.202. Eclipse 3.4.1 (Ganymede SR1) ships with version 1.1.201 of this plug-in, and hence o.j.ide.eclipse.as.ui does not load. Eclipse 3.4.2 (Ganymede SR2) ships will ship with version 1.1.203 of this plug-in, and hence the plug-in loads and works correctly. The question here for JBT 3 is whether the 1.1.202 version of this WTP dependency is *really* required for this plug-in to work correctly (it wasn't required for CR2, so this change happened between CR2 and today). If not (and regardless of whether there are bug fixes in this later version of WTP that we'd like to recommend to users), then the minimum version should be set back to the 1.1.201 level. Since the Eclipse 3.4.2 (Gaynmede SR2) J2EE package will be available within the next few days, users will have ready access to a complete base platform with this dependency version, but, if we are going to require a specific bug fix version of WTP, we should be careful to note that in the installation dependencies. Finally, regarding version dependencies, I'd note that it is common in Eclipse *not* to specify the third-place digit (thus only 1.1), since it should be rare to require a specific bug-fix version of a dependency. I notice, however, scanning through a number of JBT plug-ins, the we commonly specify the third place version number. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira