[infinispan-dev] Infinispan GUI demo not building after maven repo changes

[Galder Zamarreno]

I agree that this is not an issue with log4j itself, but lowering to 1.2.14 made those transitive dependency issues go away, at least in my env.

----- "Manik Surtani" <manik at jboss.org> wrote:

> Galder your issue is not with log4j directly.  Log4j is successfully
> pulled down (in my case, from
> http://repo1.maven.org/maven2/log4j/log4j/1.2.14/log4j-1.2.14.jar).
> 
> The issue is a transitive deps to the com.sun stuff that Log4J depends
> on, and this has implications elsewhere as well.
> 
>  
> 
> On 19 May 2010, at 18:05, galder at redhat.com wrote:
> 
> > 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-problems-in-maven-using-exclusions/
> 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 at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/infinispan-dev
> 
> --
> Manik Surtani
> manik at jboss.org
> Lead, Infinispan
> Lead, JBoss Cache
> http://www.infinispan.org
> http://www.jbosscache.org
> 
> 
> 
> 
> 
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev