[ome-devel] OMERO blitz Maven artifact dependency resolution

[Curtis Rueden]

Hi Josh,

> I'm suspecting that not all of OME's maven repositories are showing up
> in the virtual "/repo" repository.

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?

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.

> Is having those exclusions in the client pom going to be a workable
solution?
> If not, what would you suggest?

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.

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.

In the short term, I'll try to proceed with a dependency on omero:blitz
together with those exclusions, and see how things work!

Thanks,
Curtis


On Mon, Jun 9, 2014 at 4:00 AM, Josh Moore <josh at glencoesoftware.com> wrote:

>
> On Jun 5, 2014, at 6:17 PM, Curtis Rueden wrote:
>
> > Hi all (esp. Josh),
>
> Hi Curtis,
>
> > Thank you very much for making the OMERO libraries available as Maven
> > artifacts. It will make developing Java libraries which use OMERO much
> > easier!
> >
> > I tried adding a dependency to omero:blitz:5.0.2-ice35-b26 today, but
> > unfortunately ran into some dependency resolution errors. Details here:
> > https://gist.github.com/ctrueden/94bb1d3b6b8398aa1307
>
> I think solutions for most of the problems you describe are encoded in
>
>   https://github.com/ome/pom-omero-client/blob/dev_5_0/pom.xml
>
> Is having those exclusions in the client pom going to be a workable
> solution?
> If not, what would you suggest?
>
>
> > The four problematic dependencies are:
> > * ome:bio-formats:jar:5.0.2-ice35-b26
> > * hsqldb:hsqldb:jar:1.8.0.2
> > *
> >
> org.springframework:org.springframework.context.support:jar:3.0.1.RELEASE-A
> > * org.springframework.ldap:spring-ldap:jar:1.3.0.RELEASE-all
> >
> > I searched http://artifacts.openmicroscopy.org/ and
> http://search.maven.org/
> > and could not find these specific GAVs anywhere, although there are
> similar
> > artifacts in all cases:
> >
> >> ome:bio-formats:5.0.2-ice35-b26
> >
> > ome:formats-api:5.0.2 ?
> >
> >> hsqldb:hsqldb:1.8.0.2
> >
> > hsqldb:hsqldb:1.8.0.10 ?
> >
> >> org.springframework:org.springframework.context.support:3.0.1.RELEASE-A
> >
> > org.springframework:spring-context-support:3.0.1.RELEASE ?
> >
> >> org.springframework.ldap:spring-ldap:1.3.0.RELEASE-all
> >
> > org.springframework.ldap:spring-ldap:1.3.0.RELEASE ?
> >
> > Any suggestions on how to get this working?
>
> 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.
>
>
> > Thanks,
> > Curtis
>
> Cheers,
> ~Josh.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openmicroscopy.org.uk/pipermail/ome-devel/attachments/20140611/18777468/attachment.html>