Eclipse building - exclude can from packaging, but include in final product
I am using a local (embedded) Derby database for one of my RCP projects. The database is in the project folder structure in eclipse and checked for inclusion in the assembly.
My folder structure in Eclipse:
projectname
I
I- src
I
I- database
I I
I I-project database here
I
I
I- icons
...
The Eclipse build process now includes the database folder, including subfolders, in the project jar file.
Unfortunately, I can't convince Derby to look inside the packaged jar file and use a database there, so I would like to have a database that I use and populate when developing software, excluding the jar from the packaging, but including in the post build product.
My dream was for the product folder structure to look like this:
productname
I
I- configuration
I
I- database ...!
I
I- jre
I
I- p2
I
I- plugins
I
I- artifacts.xml
I- productname.exe
I- productname.ini
Can this be achieved with a PDE build process? Thanks!
a source to share
I don't have a complete answer, but I can offer some suggestions.
First, you can create a new plug-in that only contains your database. Then you can export this plugin as a nested (folder based) plugin rather than as a jar. This will allow Derby to access the database files, and you can selectively include the plug-in when you create your product.
Another option that might be worth investigating is not being able to connect data to objects. The features seem to offer a mechanism where you can manage individual plugins separately from plugins, and this is supported by update sites. I haven't used the object myself, but there is some interest here that might be of interest: http://dev.eclipse.org/mhonarc/lists/platform-update-dev/msg00807.html
a source to share