Hi Mark (resending I did not cc the list),
> Are there guidelines for plugin developers to follow?
The development section[1] of the wiki is, in general, intended to
provide these guidelines. The versioning page[2] in particular is
relevant here, along with the Fiji contribution requirements[3].
That page refers to plugins exposing APIs. What if I do not want others
to use my code as a library? Should I put everything in an "internal"
package?
>Will the updater figure it out that this is the same plugin?
Yes - if you use one of the patterns on the versioning page then the
updater will do the right thing and determine it's a new version of
the same jar.
How does it deal with the "SNAPSHOT" designation? Does it see that as a
separate plugin?
Best,
Nico
Hope that helps.
Best,
Mark
[1] http://imagej.net/Development
[2] http://imagej.net/Versioning
[3]
http://imagej.net/Fiji_contribution_requirements#Versioning_and_dependency_convergence
On Thu, Jul 30, 2015 at 2:38 PM, Nico Stuurman <nico.stuur...@ucsf.edu
<mailto:nico.stuur...@ucsf.edu>> wrote:
What is the recommended strategy for versioning of plugins? For
instance, I set up a maven project for my plugin, create a jar
(named myplugin_-0.1-SNAPSHOT.jar) and make that available through
the Fiji updater. I then make some changes and want to increase
the version in my pom.xml file (lets say to 0.1.1-SNAPSHOT). This
will change the name of the jar. Will the updater figure it out
that this is the same plugin? Are there guidelines for plugin
developers to follow?
Thanks!
Nico
_______________________________________________
ImageJ-devel mailing list
ImageJ-devel@imagej.net <mailto:ImageJ-devel@imagej.net>
http://imagej.net/mailman/listinfo/imagej-devel
--
Nico Stuurman
Vale lab, UCSF/HHMI
Genentech Hall, N316, MC2200
600 - 16th Street
San Francisco, CA 94158-2517
415 514 3927
nico.stuur...@ucsf.edu
_______________________________________________
ImageJ-devel mailing list
ImageJ-devel@imagej.net
http://imagej.net/mailman/listinfo/imagej-devel
