Multiple Plugins in one Dev manifest

[tmiranda]

How do you put two plugins (one Standard, one STVi) into a single SageTVPluginsDev.xml manifest? I tried just sticking two sets of <SageTVPlugin></SageTVPlugin> tags but sage ignores the second plugin altogether.

What I've been doing is creating two separate manifests, installing the first, overwriting the manifest and then installing the second. There has to be a better way.

What are others doing?

[evilpenguin]

I use multiple plugins in my dev manfiests pretty often, you must have just had an accidental XML parse error when you tried it.

[Slugger]

If including just one plugin in your SageTVPluginsDev.xml then you don't have to wrap it in a <PluginRepository> tag, you can just insert it in the file with <SageTVPlugin> as the root node of the xml doc. This is what I always did until I needed to add multiple plugins to my dev xml and discovered that you need to wrap more than one in a <PluginRepository> tag. Putting just one plugin inside <PluginRepository> is also valid and I suspect it was expected that this would always happen and the fact that it works without the <PluginRepository> tag for the case of just one plugin is a convenient accident.

In other words, your SageTVPluginsDev.xml must look like this:

<PluginRepository>
   <SageTVPlugin>
      ...
   </SageTVPlugin>
   <SageTVPlugin>
      ...
   </SageTVPlugin>
   <SageTVPlugin>
      ...
   </SageTVPlugin>
</PluginRepository>

Instead of like this:

<SageTVPlugin>
   ...
</SageTVPlugin>
<SageTVPlugin>
   ...
</SageTVPlugin>
<SageTVPlugin>
   ...
</SageTVPlugin>

[tmiranda]

I wasn't using the PluginRepository tag. Thanks.

[GKusnick]

As Slugger says (and as documented on the last page of the plugin developer's guide), the format of SageTVPluginsDev.xml is the same as that of SageTVPlugins.xml, i.e. you need to wrap the whole file in <PluginRepository> tags. (This is also basic XML. A file can contain only one root node.)

It's actually pretty straightforward to write a script that takes several manifest files from (say) a given directory and concatenates them together with the necessary <PluginRepository> tags to produce a valid repository file. You can then make running this script an automatic part of your normal build procedure, so that SageTVPluginsDev.xml is always up to date with the results of your latest build.