eclipse-fragment

Java 7u55 Eclipse System Fragment Classloader

半城伤御伤魂 提交于 2020-01-11 03:32:10
问题 In previous versions of Java I was able to use a fragment that had a host of system-bundle in order to provide classes to the boot classloader. In my particular case this was to support using Jacorb in Eclipse. This all worked fine prior to Java 7u55. I created an osgi fragment that contained all the jars for Jacorb. The manifest looks like this: Manifest-Version: 1.0 Bundle-ManifestVersion: 2 Bundle-Name: org.jacorb.systemFragment Bundle-SymbolicName: org.jacorb.systemFragment Bundle-Version

Where should I put testcode for an Eclipse plugin fragment?

妖精的绣舞 提交于 2019-12-13 16:28:32
问题 There are several posts I found while searching for best practice of where to put test code for an Eclipse plugin. Most of them suggest fragments like this I have a plugin single sourced and it has two fragments, one for RCP and one for RAP. Now if I create another fragment for testing I cannot access the RCP fragment API from the test fragment. There is a header Eclipse-ExtensibleAPI , if set to true the host plugin will make its fragment APIs available. But it's available to other plugins

Is there an equivalent to BundleActivator for Eclipse fragment projects?

放肆的年华 提交于 2019-12-10 09:23:39
问题 I am building an Eclipse plug-in that provides a set of core features in the regular plug-in project. The optional features I am providing via fragment projects. But I need the fragments to register themselves with the main plug-in on start-up. I cannot have a Bundle-Activator in the fragment project. So I am wondering is there some alternate mechanism to declare an entry point or some call-back that I can hook? And if there is no alternative other than converting the fragment project to a

Is there an equivalent to BundleActivator for Eclipse fragment projects?

末鹿安然 提交于 2019-12-05 15:15:57
I am building an Eclipse plug-in that provides a set of core features in the regular plug-in project. The optional features I am providing via fragment projects. But I need the fragments to register themselves with the main plug-in on start-up. I cannot have a Bundle-Activator in the fragment project. So I am wondering is there some alternate mechanism to declare an entry point or some call-back that I can hook? And if there is no alternative other than converting the fragment project to a regular plug-in project is there a downside that I need to be aware of? This is the solution I used based