Avoid using log4j 1.2.15. It has a broken pom which sucks in some dependencies that don’t exist in public repositories.
Either use 1.2.14 or 1.2.16/17. Steve C > On 25 Aug 2015, at 2:25 am, Magnanao, Hector <[email protected]> wrote: > > Why does Maven complain with this error when I try to use version 1.2.15 of > log4j as a dependency in my pom file ? Is there a different way of uploading > this particular version of log4j ? > > [INFO] > ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] > ------------------------------------------------------------------------ > [INFO] Total time: 0.373 s > [INFO] Finished at: 2015-08-24T11:20:17-05:00 > [INFO] Final Memory: 6M/246M > [INFO] > ------------------------------------------------------------------------ > [ERROR] Failed to execute goal on project foundation: Could not resolve > dependencies for project com.mycompany.app:foundation:jar:1.0-SNAPSHOT: The > following artifacts could not be resolved: javax.jms > :jms:jar:1.1, com.sun.jdmk:jmxtools:jar:1.2.1, com.sun.jmx:jmxri:jar:1.2.1: > Could not transfer artifact javax.jms:jms:jar:1.1 from/to java.net > (https://maven-repository.dev.java.net/nonav/repository): > Cannot access https://maven-repository.dev.java.net/nonav/repository with > type legacy using the available connector factories: > BasicRepositoryConnectorFactory: Cannot access https://maven-repository. > dev.java.net/nonav/repository with type legacy using the available layout > factories: Maven2RepositoryLayoutFactory: Unsupported repository layout > legacy -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e > switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > > Hector Magnanao Jr. > SCM Analyst > > Fieldglass, Inc. > O: (331) 702-6142 > M: (773) 474-3051 > [email protected] > www.fieldglass.com > > Fieldglass is now part of SAP > > This email contains confidential information. If you are not the intended > recipient, do not read, distribute or reproduce this transmission (including > any attachments). If you have received this email in error, please notify the > sender by email reply. > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
