<div dir="ltr">Hi Jan,<div><br></div><div>> <span style="font-family:arial,sans-serif;font-size:13px">FWIW, I justed tried to setup my own omero update site</span></div><div><span style="font-family:arial,sans-serif;font-size:13px"><br>
</span></div><div><span style="font-family:arial,sans-serif;font-size:13px">Thanks for giving that a shot.</span><span style="font-family:arial,sans-serif;font-size:13px"><br></span></div><div><span style="font-family:arial,sans-serif;font-size:13px"><br>
</span></div><div>> <span style="font-family:arial,sans-serif;font-size:13px">If you know a workaround for the second issue, I'd be happy to hear it</span></div><div><span style="font-family:arial,sans-serif;font-size:13px"><br>
</span></div><div><span style="font-family:arial,sans-serif;font-size:13px">Nope, the OMERO plugin code needs to be changed, to conform to the ImageJ updater's requirements.</span></div><div><span style="font-family:arial,sans-serif;font-size:13px"><br>
</span></div><div><span style="font-family:arial,sans-serif;font-size:13px">For now, my first priority will be getting the OMERO-5.0 update site serving the ImageJ-OMERO code -- I think I won't worry about the OMERO.insight ImageJ plugin for the time being.</span></div>
<div><span style="font-family:arial,sans-serif;font-size:13px"><br></span></div><div><span style="font-family:arial,sans-serif;font-size:13px">Regards,</span></div><div><span style="font-family:arial,sans-serif;font-size:13px">Curtis</span></div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Apr 3, 2014 at 10:22 AM, Jan Eglinger <span dir="ltr"><<a href="mailto:jan.eglinger@gmail.com" target="_blank">jan.eglinger@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Dear Josh,<br>
<br>
thanks for your reply.<div class=""><br>
<br>
On 03.04.2014, 1:19 PM, Josh Moore wrote:<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">
On Apr 2, 2014, at 5:19 PM, Jan Eglinger wrote:<br>
</div><div class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
2) May I suggest to create a Fiji update site [1] for OMERO? Currently, there is the Bio-Formats update site, but for installing the OMERO plugin, you still need to manually copy the folder into ./Fiji.app/plugins<br>
</blockquote>
<br>
It's something we've been wanting to do for quite some time. I filed another ticket and CC'd you so that you'll get a notification of when it's done:<br>
<br>
<a href="http://trac.openmicroscopy.org.uk/ome/ticket/12167" target="_blank">http://trac.openmicroscopy.<u></u>org.uk/ome/ticket/12167</a><br>
<br>
</div></blockquote>
<br>
Oh, Curtis has kindly marked this as a duplicate of this existing ticket:<br>
<a href="http://trac.openmicroscopy.org.uk/ome/ticket/9342" target="_blank">http://trac.openmicroscopy.<u></u>org.uk/ome/ticket/9342</a><br>
<br>
FWIW, I justed tried to setup my own omero update site to serve some computers in our lab, and I hit two issues:<br>
<br>
1) In the downloaded OMERO.insight-ij folder, there are a bunch of jar files in ./lib that duplicate Fiji's own dependencies. I was able to delete the following jars whose versioned counterparts are in Fiji.app/jars/ (and therefore would not be necessary on the update site):<br>
<br>
commons-codec.jar<br>
commons-io.jar<br>
ij.jar<br>
jcommon.jar<br>
jfreechart.jar<br>
JHotDraw.jar<br>
jna.jar<br>
joda-time.jar<br>
JWiz.jar<br>
kryo.jar<br>
native-lib-loader.jar<br>
netcdf.jar<br>
perf4j.jar<br>
slf4j-api.jar<br>
xalan.jar<br>
<br>
(There might be more however. commons-lang.jar is a special case, since the package name 'org.apache.commons.lang3' in the current Fiji version differs from the older version in omero-ij 'org.apache.commons.lang')<br>
<br>
2) The xml files in ./config are ignored by the updater, since only java and script files are recognized in subdirectories of plugins/ . A solution might be to serve the config files in Fiji.app/lib/ , but this would require a change in the config file loading mechanism. The other option is to allow xml files in subdirectories of plugins/ , but it would require changing the updater, and is against the current policy of allowing only plugin and script files there.<br>
<br>
If you know a workaround for the second issue, I'd be happy to hear it : )<br>
<br>
Cheers,<br>
Jan<br>
<br>
</blockquote></div><br></div>