An Eclipse plugin is needed that can act as the Derby System Home, enabling
other plugins to use derby databases for meta-data
------------------------------------------------------------------------------------------------------------------------------
Key: DERBY-897
URL: http://issues.apache.org/jira/browse/DERBY-897
Project: Derby
Type: New Feature
Components: Eclipse Plug-in
Reporter: Thomas Hallgren
Some Eclipse-plugins make use of rather complex meta-data and it would be very
beneficial to use use Derby databases as storage mechanism, especially when
transaction stability etc. is of great importance.
If a plugin wants to use a Derby database, it needs to somehow define the
System property 'derby.system.home'. This is problematic since Eclipse plugins,
created by different entities in different parts of the world, must be able to
coexist. It is therfore important to publish a 'canonical' way of sharing a
Derby System. A collision between different ways of doing this is bound to
happen sooner or later otherwise.
I propose a new Derby plugin that would expose the derby packages (short of the
internal ones) so that other plugins may express a normal plugin dependency to
it. This plugin will also define the 'derby.system.home' to appoint its own
'state location'. The current derby nature would not be used since it seems
targeted at application development rather than having several plugins sharing
the same Derby system.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
