Hi Thorsten,
On Thu, 19 Dec 2013, Thorsten Wagner wrote:
> I'm currently set up an update site for more convenient updating of the
> plugins developed in our work group. For most of the plugins, it works
> very well.
>
> However, one plugin includes the apache commons lib. This lib adds a
> pom.xml to the META-INF directory of the plugin jar file.
To be precise: this lib does not add a pom.xml to the META-INF directory
of the *plugin* jar file. It contains that pom.xml file itself.
Now, if you *include* all of the contents of apache-commons.jar, then you
also get this file.
But including the contents is a bad idea since you are prone to break
expectations about being able to upgrade individual components.
It is better to ship the apache-commons.jar in the jars/ directory via the
update site.
Incidentally, this also fixes your problem with the description because
your plugin will no longer have a pom.xml and hence you can specify your
own description in the updater.
Ciao,
Johannes
--
ImageJ mailing list:
http://imagej.nih.gov/ij/list.html