Changes v1.0.14 2006-03-29

Core Added some core functionality allowing other plugins to access bundle projects.

Changes v1.0.13 2006-03-02

Core Bug fix: Jar files where not closed after manifest was read, causing locked files. This would normally happen when making a clean build after a debug session.

Changes v1.0.12 2005-12-03

Editor/Builder Bug fix. If source had import declarations referencing internal classes, the plugin wrongly said that the parent class should be imported in the manifest. E.g. If the line import com.foo.Class1.InternalClass existed in the source the plugin would say that the package com.foo.Class1 should be imported.
Export Bug fix. The plugin did not create the parent directories needed for the export path.
Builder Bug fix. The resource hierarchy was not refreshed when the bundle jar file was built. This resulted in resource out of synch related errors when for instance CVS tried to replace a bundle project from repository.
Update Site Bug fix. Attempt to get the update site to work properly.
Launcher Bug fix. System properties are checked in order to determine what system packages are exported through the system classloader.
For Knopflerfish the following properties are checked
- org.osgi.framework.system.packages
- org.osgi.framework.system.packages.file
- org.knopflerfish.framework.system.export.all_13
For eclipse the following properties are checked
- org.osgi.framework.system.packages
Editor/Builder Bug fix. Only packages which contained java resources where allowed to be exported.
Editor/Builder Bug fix. Large bundle projects could bring eclipse to its knees, especially if the manifest editor was shown.