[infinispan-issues] [JBoss JIRA] Resolved: (ISPN-453) GUI demo build fails due to unable to locate log4j

[Galder Zamarreno (JIRA)]

     [ https://jira.jboss.org/browse/ISPN-453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Galder Zamarreno resolved ISPN-453.
-----------------------------------

    Resolution: Done


> GUI demo build fails due to unable to locate log4j
> --------------------------------------------------
>
>                 Key: ISPN-453
>                 URL: https://jira.jboss.org/browse/ISPN-453
>             Project: Infinispan
>          Issue Type: Bug
>    Affects Versions: 4.1.0.BETA1
>            Reporter: Galder Zamarreno
>            Assignee: Galder Zamarreno
>             Fix For: 4.1.0.CR1
>
>
> 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?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira