Plugin Compile and load

[SBarnes]

Does a plugin compile and get loaded into memory even if it is not enabled?

The reason I am asking is in replacing a plugin with an embedded version of a library that was a newer version I had to completely delete the old version before Jiwa would accept the new one, disabling the old and restarting didn't let it compile the new version when it was imported.

[Mike.Sheen]

Does a plugin compile and get loaded into memory even if it is not enabled?

Nope. As far as then login process goes, if it is not enabled it doesn't exist - it won't get read, compiled or loaded.

The reason I am asking is in replacing a plugin with an embedded version of a library that was a newer version I had to completely delete the old version before Jiwa would accept the new one, disabling the old and restarting didn't let it compile the new version when it was imported.

I can't see how... need some steps to reproduce to answer why you saw that behaviour.

[SBarnes]

Could copying the original version 1 to back it up but as disabled possibly cause it or two plugins both having the same embedded reference library be an issue that could cause it?

[Mike.Sheen]

Could copying the original version 1 to back it up but as disabled possibly cause it or two plugins both having the same embedded reference library be an issue that could cause it?

No - embedded references are extracted to the folder of the plugin - and loaded as part of the compilation and/or load phase - if you've copied a plugin which has embedded references, and disabled the copy then both the copied, disabled plugin and it's embedded references are not loaded.