SageTV V7 plugins and classpaths

[michaeldjcox]

If I have two sageTV plugins and one needs commons lang V1.0 library JAR and another commons lang V2.0 linrary JAR.....

...both plugins will either get V1.0 or V2.0 and so one plugin will not get the version it needs.

To put it another way - each V7 plugin and sageTV all share the same java classpath right?

It probably makes no difference if the plugins state their dependencies - the class path is the class path.

Michael

[PLUCKYHD]

Originally Posted by michaeldjcox

If I have two sageTV plugins and one needs commons lang V1.0 library JAR and another commons lang V2.0 linrary JAR.....

...both plugins will either get V1.0 or V2.0 and so one plugin will not get the version it needs.

To put it another way - each V7 plugin and sageTV all share the same java classpath right?

It probably makes no difference if the plugins state their dependencies - the class path is the class path.

Michael

Actually that is why you define a min version in your manifest. Most avoid defining a max version unless they absolutely know that a newer version doesn't work. In most cases it will unless there was a major api change. So yes stating dependencies does matter as long as the manifest is correct for plugins you should be fine.

In you example if one plugin had a min version of 1.0 and another had a min version of 2.0 2.0 would be used for both versions.