Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added OSGi metadata and expose the driver as a JDBC service using dedicated
DataSourceFactory
of OSGi Enterprise.This fixes enlarged scope of issue #71 and a related conversation thread
The bundle version is defined in
build.properties
file. We may need to do something more generic concerning version computation so as to keep all versions aligned (maven version, osgi version, ant tokens, ...).Imported and exported packages are computed automatically using
bnd
tool so as to reduce the maintenance cost of metadatas.For the need of the bundle activator, the driver is now able to deregister from the driver manager (in case the bundle is stopped/unloaded). In addition to this case, deregistering methods may be used in some other situations where class unloading is expected (JEE containers for example).
There is now a compile time dependency with osgi-core and osgi-enterprise, added in the maven pom as a 'provided' dependency.