FAO jboss-dev list: Why wasn't apache-log4j/log4j group ported to new nexus repo? What are other projects depending on log4j 1.2.15 doing about this? ----- Forwarded Message ----- From: galder(a)redhat.com To: "infinispan -Dev List" <infinispan-dev(a)lists.jboss.org&gt;, "JBoss.org development list" <jboss-development(a)lists.jboss.org&gt; Sent: Wednesday, May 19, 2010 7:05:50 PM GMT +01:00 Amsterdam / Berlin / Bern / Rome / Stockholm / Vienna Subject: [infinispan-dev] Infinispan GUI demo not building after maven repo changes Hi, FAO jboss-dev list: Why wasn't apache-log4j/log4j group ported to new nexus repo? What are other projects depending on log4j 1.2.15 doing about this? If you wipe your maven2 repo, you'll find that GUI demo does not build and this is related to the maven repo changes. Basically, the GUI demo depends on log4j 1.2.15 but we're not using the default one. Instead we're depending on http://repository.jboss.org/maven2/apache-log4j/log4j/1.2.15/ Now, the reason for that I suspect is the fact that if you depend on the standard log4j 1.2.15, you get dependency failures like this: Missing: ---------- 1) com.sun.jdmk:jmxtools:jar:1.2.1 Try downloading the file manually from: http://java.sun.com/products/JavaManagement/download.html Then, install it using the command: mvn install:install-file -DgroupId=com.sun.jdmk -DartifactId=jmxtools -Dversion=1.2.1 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=com.sun.jdmk -DartifactId=jmxtools -Dversion=1.2.1 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.infinispan:infinispan-gui-demo:jar:4.1.0-SNAPSHOT 2) log4j:log4j:jar:1.2.15 3) com.sun.jdmk:jmxtools:jar:1.2.1 2) com.sun.jmx:jmxri:jar:1.2.1 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=com.sun.jmx -DartifactId=jmxri -Dversion=1.2.1 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=com.sun.jmx -DartifactId=jmxri -Dversion=1.2.1 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.infinispan:infinispan-gui-demo:jar:4.1.0-SNAPSHOT 2) log4j:log4j:jar:1.2.15 3) com.sun.jmx:jmxri:jar:1.2.1 ---------- 2 required artifacts are missing. for artifact: org.infinispan:infinispan-gui-demo:jar:4.1.0-SNAPSHOT ---------- As http://unitstep.net/blog/2009/05/18/resolving-log4j-1215-dependency-probl... explains, these appear to be optional dependencies that log4j should have set. Issues like this might explain why we ended up building and putting our own 1.2.15 version in the old repository. The point is, what do we do about it? Any particular reason why the demo depends on version 1.2.15? Cheers, -- Galder Zamarreño Sr. Software Engineer Infinispan, JBoss Cache _______________________________________________ infinispan-dev mailing list infinispan-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/infinispan-dev _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development