Description of problem: The maven pom file installed by groovy: /usr/share/maven-poms/JPP-groovy.pom contains the following <dependency> <dependency> <groupId>antlr</groupId> <artifactId>antlr</artifactId> <version>2.7.7</version> <scope>compile</scope> </dependency> However, the antlr-tool package that is providing the antlr.jar file does not provide any maven fragments and maven poms, so when this dependency is encountered, maven can't find it: The repository system is offline but the artifact antlr:antlr:jar:2.7.7 is not available in the local repository If the dependency is marked optional: <dependency> <groupId>antlr</groupId> <artifactId>antlr</artifactId> <version>2.7.7</version> <scope>compile</scope> <optional>true</optional> </dependency> (like the other ant dependencies) it works again. For a failed build in koji see this scratch rebuild of maven-invoker-plugin: https://koji.fedoraproject.org/koji/taskinfo?taskID=4724816 This package built fine a month ago: https://koji.fedoraproject.org/koji/buildinfo?buildID=361880 so some recent changes have made maven more picky about missing dependencies to trigger this issue. Version-Release number of selected component (if applicable): groovy-1.8.7-1.fc18 How reproducible: Always Steps to Reproduce: Build a package that depends on groovy using maven (e.g. maven-invoker-plugin) Actual results: Failed build Expected results: Successful build
> However, the antlr-tool package that is providing the antlr.jar file does > not provide any maven fragments and maven poms, so when this dependency is > encountered, maven can't find it: Actually antlr package does provide POM and depmap (since version 2.7.7-24), but they are instelled in a wrong subpackage (antlr-C++ instead of antlr-tool). Reassigning to antlr component.
Fixed in antlr-2.7.7-25