ansaurus

Question

How do I stop Maven 2.x from trying to retrieve non-existent pom.xml files for dependencies every build?

Answer 1

+3 A:

Downloading a POM is really a central concept in Maven to support transitive dependencies (actually, a dependency isn't just a JAR, see 3.5.5. Maven's Dependency Management for nice details on that) so I don't know if you can prevent it.

Of course, the right thing to do would be to fix the root cause of the problem. But if you can't, maybe you can run your build in offline mode (using the -o option). Or maybe you could just "install" the artifacts in your local repository using mvn install:install-file in order to generate a POM for them (but this obviously doesn't "scale" really well).

Pascal Thivent 2010-01-26 07:53:19

Thanks Pascal. Yeah, I understand that it's a central concept, but unfortunately, as is often the case in (intentionally) siloed corporates I have no control over their Maven repository, but then again I need to be able to retrieve their build artifacts. For some dependencies it's not even clear who is responsible for them, so difficult to know who to ask! If other experts have come to the same conclusion that there is no way to do this, that's fine - at least I know that I'm not crazy.And yeah, the local hacks aren't really optimal for the scalability reasons you alude to.

Chad 2010-01-27 01:22:59

Answer 2

+3 A:

Pascal's answer is correct for two local build workarounds. However, your best option is to request the owners of these projects to create POMs for the artifacts. They don't need to be complex, the simple alternative that Maven is using internally will work:

<project>
  <modelVersion>4.0.0</modelVersion>
  <groupId>aGroupId</groupId>
  <artifactId>aArtifactId</artifactId>
  <version>4.0.14i</version>
</project>

Brett Porter 2010-01-27 00:07:38

I was hoping to avoid having to trudge around the corporation finding owners of all of the artifacts. But if there really is no way to alter this part of Maven's behaviour, I guess I'll have to do that.It just seems strange to me that Maven will accept a corrupted/incompatible local repo POM without attempting to retrieve it again, but a non-existent one it will keep trying forever, even if it succeeded in retrieving a jar.

Chad 2010-01-27 01:29:05

Answer 3

A:

Set up a Nexus Repository (or similar) and upload the artifacts there. Nexus will automatically create basic poms for artifacts you upload.

Michael Bushe 2010-07-14 17:36:04

ansaurus

tags:

views:

answers:

How do I stop Maven 2.x from trying to retrieve non-existent pom.xml files for dependencies every build?

related questions