Plugin File management

[chrishallowell]

I've got a database file that I need to install with a plugin to this directory: plugins/myplugin/. But if the database file already exists, I don't want the plugin to overwrite it. Can the plugin system handle this or do I need to manually code for this?

My plug will have a package for the STVi and a package for the JAR.

STVi.zip will have the XML file
JAR.zip will have the JAR file

If I put the database file in the JAR.zip and specify Overwrite=false in the plugin manifest, then the JAR file won't get overwritten. Right?

Do I have to put it in the JAR.zip file and write code to move it to plugins/myplugin/ if it doesn't exist and if it already exists, then just delete the file out of the JAR directory?

[stuckless]

Just put your configuration/database (ie files that you don't want to overwrite) in another .zip file and use overwrite=false for that zip only.

[GKusnick]

Why put it in the JARs directory in the first place? Your plugin can have as many packages as you need. In this case a System package seems like the appropriate vehicle for extracting the file to where you want it to be.

[chrishallowell]

Ok, I guess I wasn't thinking about a new package as an option . Thanks for pointing that out. So I can have a 3rd package of type system with overwrite=false and in the zip file have: plugins/myplugin/databasefile.db