[jbosstools-issues] [JBoss JIRA] Created: (JBIDE-471) JBoss IDE beta update site installation rejects Eclipse 3.3 Mx (... requires feature "org.eclipse.platform (3.2.0)", or equivalent)

[Arjan van Bentem (JIRA)]

JBoss IDE beta update site installation rejects Eclipse 3.3 Mx (... requires feature "org.eclipse.platform (3.2.0)", or equivalent)
-----------------------------------------------------------------------------------------------------------------------------------

                 Key: JBIDE-471
                 URL: http://jira.jboss.com/jira/browse/JBIDE-471
             Project: JBoss IDE
          Issue Type: Bug
          Components: JBossIDE Core
    Affects Versions: 2.0.0.Beta2
         Environment: Win32, Eclipse 3.3 M6
            Reporter: Arjan van Bentem
         Assigned To: Marshall Culpepper


JBoss IDE 2.0.0.Beta2 installs fine when using the update site http://download.jboss.org/jbosside/updates/development/ in Eclipse 3.2.x. However, apparently it has some hardcoded reference to a specific Eclipse version number: when using the same update site URL in Eclipse 3.3 M6 then installation halts with the errors listed at the end of this issue.

Maybe somehow relaxing the required Eclipse version will simply enable using the update site in Eclipse 3.3.x as well?


ONLY for the sake of the archives:

I did not try installing the latest version from CVS.

http://www.jboss.com/index.html?module=bb&op=viewtopic&t=102699 notes something about the dependencies in feature.xml. However, note that simply changing match="equivalent" in feature.xml is NOT sufficient. For example, the following will NOT work:

- install Web Standard Tools (WST) and J2EE Standard Tools (JST) using Help, Software Updates, Find and Install
- download a non-bundle version (such as JBossIDE-2.0.0.Beta2-ALL.zip) and unzip
- in the unzipped folder, in each feature.xml file, replace each occurrence match="equivalent" with match="greaterOrEqual"
- add a local update site using Help, Software Updates, Find and Install, and make it point to the "eclipse" subfolder of the unzipped archive (note that Eclipse caches the feature details; Eclipse needs to be restarted when changing feature.xml on the fly).
Now, all SEEMS to install fine, but it does not run as expected: some plugins are missing, and when in configuration/config.ini the line "eclipse.product=org.eclipse.sdk.ide" is replaced with "eclipse.product=org.jboss.ide.eclipse.product.product" and "jbosside.version=2.0.0.Beta2" then Eclipse does not startup (logs are created though).


JST Common Core (1.5.1.v200608082030--0842282_363739) requires feature "org.eclipse.platform (3.2.0)", or equivalent.
JST Server Core (1.5.1.v200608082030--2PD88P8UBJx787) requires feature "org.eclipse.platform (3.2.0)", or equivalent.
JST Web Core (1.5.1.v200608082030--87cMN7NRVeVWXd) requires feature "org.eclipse.platform (3.2.0)", or equivalent.
JST Enterprise Core (1.5.1.v200609051533--2PD88P8YAGDADJ) requires feature "org.eclipse.platform (3.2.0)", or equivalent.
JST Enterprise UI (1.5.1.v200608082030-pEBq_haA1H4sJf6) requires feature "org.eclipse.platform (3.2.0)", or equivalent.
WST Server Core (1.5.1.v200608082030------1G955G5L7D) requires feature "org.eclipse.rcp (3.2.0)", or equivalent.
WST XML Core (1.5.1.v200608082030--3YIAAYAjGLENFH) requires feature "org.eclipse.rcp (3.2.0)", or equivalent.
WST Web Services Core (1.5.1.v200608082030--4hNDDhDvGTJSLf) requires feature "org.eclipse.platform (3.2.0)", or equivalent.
WST Web Core (1.5.1.v200608082030--4hNDDhDvKRFXQM) requires feature "org.eclipse.platform (3.2.0)", or equivalent.
WST Relational Database Core (1.5.1.v200608082030--3YIAAYAeEKFTFU) requires feature "org.eclipse.platform (3.2.0)", or equivalent.
WST Relational Database Adapters (1.5.1.v200608082030--Cq0bcpdJw4teC8) requires feature "org.eclipse.platform (3.2.0)", or equivalent.
JBossIDE JBossAS Adapter Feature (1.0.0.Beta2) requires plug-in "org.eclipse.ui.workbench.texteditor (3.2.0)", or equivalent.


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira