I didn't notify anybody, but I'd rather have considered opening an issue with Sonatype (https://issues.sonatype.org/browse/OSSRH). I mean, it's a repo issue, not a Maven issue, right? But in any case, I don't think anybody will do anything about it. There are other broken artifacts on Maven central. My expectation would be that the person most likely to fix the situation would be the one who uploaded the broken artifact in the first place… or some third person uploading the missing dependency.
-- Richard On 12.11.2013, at 23:20, Marshall Schor <[email protected]> wrote: > Richard, thanks for tracking this down. > > Have you written about this on the maven-dev list? If not, I can write > something to alert them to this issue. > > -Marshall > > On 11/12/2013 4:17 PM, Richard Eckart de Castilho wrote: >> Thanks for testing. I verified that there is a new version of the runtime >> artifact on Maven Central, and it has a dependency to the app artifact >> which is *not* on Maven Central. >> >> http://search.maven.org/#artifactdetails%7Corg.eclipse.core%7Cruntime%7C3.9.0-v20130326-1255%7Cjar >> >> So unless somebody uploads a newer version of the runtime artifact with >> a fixed dependency or someone uploads an app artifact in version 1.0.0, >> UIMA 2.4.2 cannot be built from source. >> >> As a workaround, you can probably replace the version ranges in the >> dependencies >> on the runtime in the UIMA 2.4.2 POMs with a fixed version 3.3.100-v20070530. >> >> We need to consider how to deal with these version ranges I guess. >> >> -- Richard >> >> On 12.11.2013, at 22:11, Kim Ebert <[email protected]> wrote: >> >>> Hi Richard, >>> >>> rm -rvf ~/.m2 >>> >>> then >>> >>> mvn compile >>> >>> Same problem still. I was actually clearing the .m2 directory to verify >>> that my cache wasn't causing me any problems on a build. >>> >>> Thanks, >>> >>> Kim Ebert >>> 1.801.669.7342 >>> Perfect Search Corp >>> http://www.perfectsearchcorp.com/ >>> >>> On 11/12/2013 02:05 PM, Richard Eckart de Castilho wrote: >>>> That's what I was expecting. I assume that you have the 3.9.0-xxx version >>>> in >>>> your local .m2 repository, so the version range is resolved to that and >>>> I don't see Maven actively accessing a strange repository in your logs, >>>> so it might just be a remnant of some other project you built earlier. >>>> >>>> Try purging that version from your local .m2 repository (or maybe start >>>> with a new >>>> empty .m2 repository). >>>> >>>> -- Richard >>>> >>>> On 12.11.2013, at 21:46, Kim Ebert <[email protected]> wrote: >>>> >>>>> It appears for some reason that my version is resolving to >>>>> org.eclipse.core:runtime:jar:3.9.0-v20130326-1255:provided instead of >>>>> org.eclipse.core:runtime:jar:3.3.100-v20070530 >>>>> >>>>> The eclipse dependency is listed as: >>>>> >>>>> <!-- Eclipse dependencies --> >>>>> <dependency> >>>>> <groupId>org.eclipse.core</groupId> >>>>> <artifactId>runtime</artifactId> >>>>> <version>[3.3.0.0,4.0.0)</version> >>>>> <scope>provided</scope> >>>>> </dependency>
