<div dir="ltr">Hi Josh,<div><br></div><div><div>> I'm suspecting that not all of OME's maven repositories are showing up</div><div>> in the virtual "/repo" repository.</div></div><div><br></div><div>
Perhaps, but I have seen no evidence of that. The repo group looks pretty complete to me. Do you know of a specific artifact that is _not_ present there, but _is_ present in one of the others?</div><div><br></div><div>Anyway, commenting out the "repo" aggregate repository in favor of those defined in pom-omero-client (i.e., ome.releases, ome.snapshots, ome.external and ome.manual) yields no change. Those four problematic artifacts are still missing.</div>
<div><br></div><div><div>> Is having those exclusions in the client pom going to be a workable solution?</div><div>> If not, what would you suggest?</div></div><div><br></div><div>Adding the exclusions resolves the immediate issue. But it is a hack workaround, since anyone else consuming omero:blitz will need to do the same thing. The underlying issue is that omero:blitz:5.0.2-* has invalid dependency metadata in its POM, which I would very much favor fixing, rather than passing the buck downstream.</div>
<div><br>Furthermore, I am guessing that blitz actually _does_ depend on some Bio-Formats artifact(s) or other, which is not reflected after adding the excludes. Probably it is the same for the other three missing artifacts, too? Blitz actually does depend on those projects, just not those specific GAV formulations. So excluding them papers over the problem and opens the door to ClassNotFoundException etc. when attempting to perform certain actions using the Blitz API.</div>
<div><br></div><div>In the short term, I'll try to proceed with a dependency on omero:blitz together with those exclusions, and see how things work!</div><div><br></div><div>Thanks,</div><div>Curtis</div></div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Mon, Jun 9, 2014 at 4:00 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 Jun 5, 2014, at 6:17 PM, Curtis Rueden wrote:<br>
<br>
> Hi all (esp. Josh),<br>
<br>
Hi Curtis,<br>
<div class=""><br>
> Thank you very much for making the OMERO libraries available as Maven<br>
> artifacts. It will make developing Java libraries which use OMERO much<br>
> easier!<br>
><br>
> I tried adding a dependency to omero:blitz:5.0.2-ice35-b26 today, but<br>
> unfortunately ran into some dependency resolution errors. Details here:<br>
> <a href="https://gist.github.com/ctrueden/94bb1d3b6b8398aa1307" target="_blank">https://gist.github.com/ctrueden/94bb1d3b6b8398aa1307</a><br>
<br>
</div>I think solutions for most of the problems you describe are encoded in<br>
<br>
<a href="https://github.com/ome/pom-omero-client/blob/dev_5_0/pom.xml" target="_blank">https://github.com/ome/pom-omero-client/blob/dev_5_0/pom.xml</a><br>
<br>
Is having those exclusions in the client pom going to be a workable solution?<br>
If not, what would you suggest?<br>
<div class=""><br>
<br>
> The four problematic dependencies are:<br>
> * ome:bio-formats:jar:5.0.2-ice35-b26<br>
> * hsqldb:hsqldb:jar:1.8.0.2<br>
> *<br>
> org.springframework:org.springframework.context.support:jar:3.0.1.RELEASE-A<br>
> * org.springframework.ldap:spring-ldap:jar:1.3.0.RELEASE-all<br>
><br>
> I searched <a href="http://artifacts.openmicroscopy.org/" target="_blank">http://artifacts.openmicroscopy.org/</a> and <a href="http://search.maven.org/" target="_blank">http://search.maven.org/</a><br>
> and could not find these specific GAVs anywhere, although there are similar<br>
> artifacts in all cases:<br>
><br>
>> ome:bio-formats:5.0.2-ice35-b26<br>
><br>
> ome:formats-api:5.0.2 ?<br>
><br>
>> hsqldb:hsqldb:1.8.0.2<br>
><br>
> hsqldb:hsqldb:1.8.0.10 ?<br>
><br>
>> org.springframework:org.springframework.context.support:3.0.1.RELEASE-A<br>
><br>
> org.springframework:spring-context-support:3.0.1.RELEASE ?<br>
><br>
>> org.springframework.ldap:spring-ldap:1.3.0.RELEASE-all<br>
><br>
> org.springframework.ldap:spring-ldap:1.3.0.RELEASE ?<br>
><br>
> Any suggestions on how to get this working?<br>
<br>
</div>In addition, I'm suspecting that not all of OME's maven repositories are showing up in the virtual "/repo" repository. I'll look into this first and get back to you. If you want to move forward by using the repositories set in pom-omero-client/pom.xml, let me know if any of the above issues are solved.<br>
<br>
<br>
> Thanks,<br>
> Curtis<br>
<br>
Cheers,<br>
~Josh.<br>
</blockquote></div><br></div>