| Install files that may not be overwritten by later updates [message #671342] |
Tue, 17 May 2011 15:05 |
 Marijn Bekers
Messages: 1
Registered: July 2009 |
Junior Member |
|
|
I'd like to include an sqlite database with my RCP product that is updated via p2.
Using root.folder, I added a 'data' folder to my application feature that contains the sqlite file.
When I export my product base on the feature, the sqlite file is correctly included in the exported package.
However, when I increase the version number of the feature and product into the repository and then try to update, the update fails because it tries to replace the sqlite file (it is locked by the background service that has a connection to the DB).
I'd like to skip updating this file altogether after installation: I do not want the user's data that may have been entered into the database file to be overwritten.
Is there a p2 way of delivering initial versions for user-managed files, which will never be updated after the initial installation?
I'm not even sure what the correct terminology is, so searching has not given me any meaningful results.
|
|
|
Powered by
FUDForum. Page generated in 0.02768 seconds