[
https://jira.jboss.org/jira/browse/JBDS-533?page=com.atlassian.jira.plugi...
]
Snjezana Peco commented on JBDS-533:
------------------------------------
If eclipse.ini and config.ini are added to JBDS that has been started at least once, P2
will be configured and Equinox Transforms will work correctly.
However, a problem occurs when Eclipse starts the first time within a product that
isn't P2 enabled such as JBDS.
bundles.info doesn't contain any data about the transforms plugins. That's why the
P2 engine throws the error "java.lang.IllegalStateException: The state indicates the
bundle is resolved"
This is probably a bug in P2. In my opinion, plugins that are added to osgi.bundles should
have been started independently of P2.
The solution is to add these bundles to bundles.info. It is necessary to add the following
three lines:
org.eclipse.equinox.transforms.hook,1.0.0.v20080610,file:plugins\org.eclipse.equinox.transforms.hook_1.0.0.v20080610.jar,4,false
org.eclipse.equinox.transforms.xslt,1.0.0.v20080610,file:plugins\org.eclipse.equinox.transforms.xslt_1.0.0.v20080610.jar,1,true
org.jboss.tools.equinox.transforms.xslt,3.0.0.CR1-R200812191548,file:plugins\org.jboss.tools.equinox.transforms.xslt_3.0.0.CR1-R200812191548.jar,1,true
Be sure that org.jboss.tools.equinox.transforms.xslt contains the correct version ( in
this example, it is 3.0.0.CR1-R200812191548).
Another problem is that P2 changes config.ini when reconfiguring bundles.info (it removes
org.eclipse.equinox.transforms.xslt and org.jboss.tools.equinox.transforms.xslt from
osgi.bundles).
This can be solved by adding osgi.bundles to the eclipse.ini file.
The eclipse.ini file would look as follows:
-framework
plugins\org.eclipse.osgi_3.4.2.R34x_v20080826-1230.jar
-vmargs
-Xms128m
-Xmx512m
-XX:MaxPermSize=128m
-Dosgi.bundles=reference:file:org.eclipse.equinox.simpleconfigurator_1.0.0.v20080604.jar@1:start,org.eclipse.equinox.transforms.xslt@1:start,org.jboss.tools.equinox.transforms.xslt@1:start
NOTE
-Dosgi.bundles=... is one line
Equinox Transforms plugin for JBDS
----------------------------------
Key: JBDS-533
URL:
https://jira.jboss.org/jira/browse/JBDS-533
Project: Developer Studio
Issue Type: Feature Request
Affects Versions: 2.0.0.cr1
Reporter: Rob Stryker
Assignee: Snjezana Peco
Priority: Critical
Fix For: 2.0.0.cr1
Attachments: config.ini, eclipse.ini, org.jboss.tools.runtime_1.0.0.jar
Develop a plugin which will be able to transform / invalidate other plugins in an
installation. First iteration could be just a core with a hard-coded list of plugins /
extension points which we want invalidated.
The goal here is to have all appropriate plugins in our installation, but disable the
ones we do not want. Currently, JBDS removes the webtools jboss server-tools jar entirely,
which makes the update site fail. What we need here is to have the webtools jboss
server-tools jar IN hte installation, and loaded as a plugin, but have all of its
extension points invalidated so it is effectively an empty non-contributing plugin.
org.eclipse.jst.server.generic.jboss_1.5.205.v200805140145 is the plugin we need
invalidated. We need it's plugin.xml to be essentially empty with just base
<plugin></plugin> tags.
--
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