How are you guys handling plugin import

[PLUCKYHD]

Anyone else have a specific task they would only like to fire in the plugin implementation on initial import of the plugin? How are you doing this? I thought about a properties file but could see that hitting some hitches as I really only want to fire this on initial import and not every time start() is called. Just curious how others were doing it?

[jreichen]

For Jetty I migrate the properties from JettyStarter.properties to Sage.properties if the JettyStarter.properties file exists and the jetty/jetty.configfiles property doesn't exist in Sage.properties yet. This works fine for me and is probably better because I can retest it just by cleaning out Sage.properties.

[PLUCKYHD]

Originally Posted by jreichen

For Jetty I migrate the properties from JettyStarter.properties to Sage.properties if the JettyStarter.properties file exists and the jetty/jetty.configfiles property doesn't exist in Sage.properties yet. This works fine for me and is probably better because I can retest it just by cleaning out Sage.properties.

Good idea I can easily check for the existence of a couple of directories in my case on initial startup.

[GKusnick]

Seems to me that "run once on first install" is the wrong way to look at it. A better way is to ask if any old junk exists, and if so, get rid of it. Then if some of that junk mysteriously reappears for whatever reason (e.g. because the user restored from a backup, or tried to revert to an older version of your plugin), your code knows to get rid of it again, regardless of whether that code has run once already. And it's not like it does any harm to check for old junk every time time start() is called.

[PLUCKYHD]

Originally Posted by GKusnick

Seems to me that "run once on first install" is the wrong way to look at it. A better way is to ask if any old junk exists, and if so, get rid of it. Then if some of that junk mysteriously reappears for whatever reason (e.g. because the user restored from a backup, or tried to revert to an older version of your plugin), your code knows to get rid of it again, regardless of whether that code has run once already. And it's not like it does any harm to check for old junk every time time start() is called.

Well in my case it is just scaling images on the first time start is called the rest of the time it is done on listeners and I really don't want scaling done every time start is gone. So yeah basically I will check if the scaling folders exist already on start.