I said it way back in 2009, and it is still true: Friends don't let friends use the dev.java.net repo.
Seriously, get rid of that repo from all your pom files, config files, everywhere. Find another source of the javax.jms jar that you need, or try a newer version, perhaps under a different groupId. Wayne On Mon, Aug 24, 2015 at 11:40 AM, Adrien Rivard <[email protected]> wrote: > Hi, > > It is hard to say for sure without the pom but, it look like you are trying > to use (maybe indirectly) an invalid repository / repositoryUrl ( > https://maven-repository.dev.java.net/nonav/repository is not accessible > for me at least). > Error don't appear to be related with log4j but with javax.jms:jms:jar:1.1 > though. > > > > > On Mon, Aug 24, 2015 at 6:25 PM, 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. >> >> > > > -- > Adrien Rivard --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
