Hi folks, In a clean maven 2.2.1 installation (on Fedora/Linux in this case), I'm having problems with some dependencies from maven central that depend on the maven repo at https://maven-repository.dev.java.net/nonav/repository/.
Steps to reproduce: 1) Rename your ~/.m2 folder to something else in order to start with a vanilla maven installation. 2) Create a very minimalistic POM that depends on log4j: <project xmlns="http://maven.apache.org/POM/4.0.0";> <modelVersion>4.0.0</modelVersion> <groupId>com.example</groupId> <artifactId>example</artifactId> <version>1.0-SNAPSHOT</version> <packaging>jar</packaging> <dependencies> <dependency> <groupId>log4j</groupId> <artifactId>log4j</artifactId> <version>1.2.15</version> </dependency> </dependencies> </project> 3) run mvn dependency:resolve Outcomes: Maven gets a 301 http status code from artifacts in the java.net repository (search for CHECKSUM FAILED in the logs), but saves the html content of that redirect inplace of the POM/jar, leading to junk in your local repository. Is this a known issue? Is it even legal for a POM in maven central to have dependencies outside of central? I solved this for my own projects by adding a mirror section in settings.xml pointing to the sonatype java.net mirror. cheers, asgeir --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
