Support for eclipse-3.5: Galileo
--------------------------------
Key: PAXRUNNER-265
URL: http://issues.ops4j.org/browse/PAXRUNNER-265
Project: Pax Runner
Issue Type: Improvement
Components: eclipse plugin
Affects Versions: 0.20.0
Reporter: Hugues Malphettes
Assignee: Alin Dreghiciu
Attachments: pax-runner-eclipse_pax-runner-eclipse-core_src.diff
Hi there.
I am trying to add support for the next version of eclipse: Galileo
eclipse-3.5.
It seems the only things to change are inside the
pax-runner-eclipse/pax-runner-eclipse-core fragment.
There are 2 API changes in the pde plugin. In the suggested fix I am using
introspection to discover if the 3.4 or the 3.5 API should be used.
If you don't mind having 2 versions of this fragment then the changes are a bit
simpler.
The last change is to locate the built bundles.
With 3.5 when a new bundle is created, the version is by default 1.0.0.qualifier
This string is processed specifically by pde to replace the qualifier by a
timestamp.
The suggested fix to be able to locate the bundle when it uses such version
consists of looking at all the jars generated and selecting the most recent one
that matches the bundle name we are looking for.
I am afraid that I have not been able to test those changes: I cannot find a
0.6.0-SNAPSHOT version of pax.url. I replaced it by a 0.5.2 version.
I could not find either a version of pax.cache and so currently after my fixes,
in eclipse-3.5-RC1 I know the bundles are exported and located but it fails
with this trace (I inserted the e.printStackTrace() to get that trace):
java.lang.RuntimeException: Could not create [handler.cache]
at org.ops4j.pax.runner.Run.createActivator(Run.java:709)
at org.ops4j.pax.runner.Run.installHandlers(Run.java:337)
at org.ops4j.pax.runner.Run.start(Run.java:214)
at org.ops4j.pax.runner.Run.main(Run.java:147)
at
org.ops4j.pax.cursor.LaunchConfiguration$1.run(LaunchConfiguration.java:233)
at
org.eclipse.pde.ui.launcher.AbstractPDELaunchConfiguration.launch(AbstractPDELaunchConfiguration.java:83)
at
org.eclipse.pde.ui.launcher.OSGiLaunchConfigurationDelegate.launch(OSGiLaunchConfigurationDelegate.java:43)
at
org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:853)
at
org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:703)
at
org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:866)
at
org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1069)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: java.lang.ClassNotFoundException:
org.ops4j.pax.url.cache.internal.Activator
at
org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:489)
Let me know if you are interested by this contribution and if you let me know
where I can locate the missing bundles, I'd be happy to test it further.
Thanks.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.ops4j.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
general mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/general
