Community
Participate
Working Groups
Build Identifier: 20100617-1415 This worked fine with Eclipse 3.5.2: Class A from a plugin was replaced from it's equivalent in a patch fragment. Under 'Run configurations' I had both the plugin and the patch fragment selected under 'Workspace' not 'Patch fragment' in order not to export the plugin every time I made a change to it. This feature seems to be broken in Eclipse 3.6 as only Class A gets loaded and the patch fragment is ignored. When selecting the plugin and the patch fragment under 'Target platform', the replacement works as expected. Reproducible: Always Steps to Reproduce: 1. create a plugin and a patch fragment 2. create class A in the plugin that can be replaced 3. create class A in the patch fragment that replaces class A from the plugin 4. in 'Run configurations' select both under 'Workspace', not 'Target platform'
This bug is still not fixed in Eclipse 3.6.1 and prevents fluent development.
This bug persists also in Eclipse 3.7 and prevents fluent development!
Equinox seems to cause this.
I have found the cause for the behaviour described before: My RCP application still used the Target Platform 3.5.2, while I used Eclipse 3.6.2 and then 3.7 Updating to the matching Target Platform for Eclipse, all works fine now. I'm sorry for polluting the bugtracker with this!
