<div dir="ltr"><div><span style="font-family:arial,sans-serif;font-size:13px">Hi Josh,</span></div><div><span style="font-family:arial,sans-serif;font-size:13px"><br></span></div><div>> Sure. But this is an after-the-fact release, so I'd really prefer to</div>
<div>> not be mucking with what's defined in the ivy.xml and pom.xml files.</div><div><br></div><div>Right. To clarify: I meant to fix the hacks for 5.0.3. Not to somehow rewrite 5.0.2, which is now writ in stone.</div>
<div><br></div><div><div>> Am I misunderstanding the function of</div><div>> <a href="https://github.com/ome/pom-omero-client/blob/dev_5_0/pom.xml#L97">https://github.com/ome/pom-omero-client/blob/dev_5_0/pom.xml#L97</a> ?</div>
<div>> Does that not re-add the dependency?</div></div><div><br></div><div>Well, if someone extends pom-omero-client, _and_ they add a dependency on that specific GA, _then_ they won't need to declare the version because it is managed by the parent. But it won't automagically add the dependency for them. To do that, you'd have to declare it in a <dependencies> section rather than a <dependencyManagement> section which is considered very bad practice, since someone might theoretically extend pom-omero-client without actually wanting that dependency.</div>
<div><br></div><div>Anyway, the way forward to is to fix the dependency metadata for 5.0.3.</div><div><br></div><div>Regards,</div><div>Curtis</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Jun 11, 2014 at 3:52 PM, 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"><div class=""><br>
On Jun 11, 2014, at 10:43 PM, Curtis Rueden wrote:<br>
<br>
> same thing. The underlying issue is that omero:blitz:5.0.2-* has invalid<br>
> dependency metadata in its POM, which I would very much favor fixing,<br>
> rather than passing the buck downstream.<br>
<br>
</div>Sure. But this is an after-the-fact release, so I'd really prefer to not be mucking with what's defined in the ivy.xml and pom.xml files. I'm just in the process of setting up our daily snapshot builds after which, we can start testing against those and incrementally remove the hacks.<br>
<div class=""><br>
<br>
> Furthermore, I am guessing that blitz actually _does_ depend on some<br>
> Bio-Formats artifact(s) or other, which is not reflected after adding the<br>
> excludes. Probably it is the same for the other three missing artifacts,<br>
> too? Blitz actually does depend on those projects, just not those specific<br>
> GAV formulations. So excluding them papers over the problem and opens the<br>
> door to ClassNotFoundException etc. when attempting to perform certain<br>
> actions using the Blitz API.<br>
<br>
</div>Am I misunderstanding the function of <a href="https://github.com/ome/pom-omero-client/blob/dev_5_0/pom.xml#L97" target="_blank">https://github.com/ome/pom-omero-client/blob/dev_5_0/pom.xml#L97</a> ?<br>
Does that not re-add the dependency?<br>
<div class="im HOEnZb"><br>
<br>
> In the short term, I'll try to proceed with a dependency on omero:blitz<br>
> together with those exclusions, and see how things work!<br>
<br>
Thanks,<br>
</div><span class="HOEnZb"><font color="#888888">~Josh.<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
> Thanks,<br>
> Curtis<br>
><br>
><br>
> On Mon, Jun 9, 2014 at 4:00 AM, Josh Moore <<a href="mailto:josh@glencoesoftware.com">josh@glencoesoftware.com</a>> wrote:<br>
><br>
>><br>
>> On Jun 5, 2014, at 6:17 PM, Curtis Rueden wrote:<br>
>><br>
>>> Hi all (esp. Josh),<br>
>><br>
>> Hi Curtis,<br>
>><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>
>> 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<br>
>> solution?<br>
>> If not, what would you suggest?<br>
>><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>
>>><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<br>
>> <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<br>
>> 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>
>> In addition, I'm suspecting that not all of OME's maven repositories are<br>
>> showing up in the virtual "/repo" repository. I'll look into this first and<br>
>> get back to you. If you want to move forward by using the repositories set<br>
>> in pom-omero-client/pom.xml, let me know if any of the above issues are<br>
>> solved.<br>
>><br>
>><br>
>>> Thanks,<br>
>>> Curtis<br>
>><br>
>> Cheers,<br>
>> ~Josh.<br>
>><br>
<br>
</div></div></blockquote></div><br></div>