<div dir="ltr">+1 vote for maven for me too. I realize it's not so easy considering the tools you need to autogenerate source from schema. Client-side usage as well for me.<div><br></div><div>Thanks,</div><div>--Lee</div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Aug 30, 2013 at 11:03 AM, Josh Moore <span dir="ltr"><<a href="mailto:josh@glencoesoftware.com" target="_blank">josh@glencoesoftware.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
On Aug 29, 2013, at 10:07 PM, Curtis Rueden wrote:<br>
<br>
> Hi all,<br>
<br>
Hi Curtis,<br>
<br>
> I would like to depend on some of OMERO's components for communicating with<br>
> the OMERO server, particularly blitz.jar, from my Java code. However,<br>
> blitz.jar has many dependencies of its own.<br>
<br>
Are you developing something for the client-side or the server-side?<br>
<br>
> Is there a release version in a Maven repository that I can use for my<br>
> Maven-based project?<br>
<br>
Not yet, unfortunately.<br>
<br>
> If not, what is the recommended way of managing OMERO components as<br>
> dependencies?<br>
<br>
Assuming this is for the client-side (i.e. it won't run with the server), you'll need the contents of lib/client on your CLASSPATH. For compiling functionality into your server, see <a href="https://github.com/joshmoore/ome-cmd-example" target="_blank">https://github.com/joshmoore/ome-cmd-example</a><br>
<br>
> Thanks,<br>
> Curtis<br>
<br>
Cheers,<br>
~Josh.<br>
_______________________________________________<br>
ome-devel mailing list<br>
<a href="mailto:ome-devel@lists.openmicroscopy.org.uk">ome-devel@lists.openmicroscopy.org.uk</a><br>
<a href="http://lists.openmicroscopy.org.uk/mailman/listinfo/ome-devel" target="_blank">http://lists.openmicroscopy.org.uk/mailman/listinfo/ome-devel</a><br>
</blockquote></div><br></div>