The following artifacts could not be resolved javax jms jms jar 1 1

Question

I am trying to compile a maven project  but I systematically get the following error message    ERROR Failed to execute goal on project      Could not resolve dependencies for project     war 1 0 0  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  Failure to find javax jms jms jar 1 1 in http   mirrors ibiblio org maven2    was cached in the local repository  resolution will not be reattempted until   the update interval of maven2-repository ibiblio mirror has elapsed or   updates are forced - gt   Help 1    I know about this maven post about Sun jars  but it does not solve the problem   Is there a repository I can specify in my pom xml

User · Answer

If anyone still wants to use jms1 1 then add the public jboss repository and maven will find it     project- dependencies      lt dependencies gt       lt dependency gt         lt groupId gt javax jms lt  groupId gt         lt artifactId gt jms lt  artifactId gt         lt version gt 1 1 lt  version gt       lt  dependency gt    project- repositories      lt repositories gt       lt repository gt         lt id gt repository jboss org-public lt  id gt         lt name gt JBoss org Maven repository lt  name gt         lt url gt https   repository jboss org nexus content groups public lt  url gt       lt  repository gt      It works -  F  mvn-repo-stuff gt mvn verify  INFO  Scanning for projects     INFO   INFO  ------------------------------------------------------------------------  INFO  Building mvn-repo-stuff 1 0-SNAPSHOT  INFO  ------------------------------------------------------------------------ Downloading  http   repo1 maven org maven2 javax jms jms 1 1 jms-1 1 pom Downloaded  http   repo1 maven org maven2 javax jms jms 1 1 jms-1 1 pom  677 B at 0 8 KB sec   WARNING  The artifact xml-apis xml-apis jar 2 0 2 has been relocated to xml-apis xml-apis jar 1 0 b2 Downloading  http   repo1 maven org maven2 javax jms jms 1 1 jms-1 1 jar Downloading  https   repository jboss org nexus content groups public javax jms jms 1 1 jms-1 1 jar Downloaded  https   repository jboss org nexus content groups public javax jms jms 1 1 jms-1 1 jar  26 KB at 8 5 KB sec

User · Answer

Thanks for the suggestions  I finally found a solution to this problem after reading this  It turns out that these dependencies were coming from a dependency to ZooKeeper   I modified my pom xml as following and it solved the problem        lt dependency gt           lt groupId gt org apache zookeeper lt  groupId gt           lt artifactId gt zookeeper lt  artifactId gt           lt version gt 3 3 2 lt  version gt           lt exclusions gt               lt exclusion gt                   lt groupId gt com sun jmx lt  groupId gt                   lt artifactId gt jmxri lt  artifactId gt               lt  exclusion gt               lt exclusion gt                   lt groupId gt com sun jdmk lt  groupId gt                   lt artifactId gt jmxtools lt  artifactId gt               lt  exclusion gt               lt exclusion gt                   lt groupId gt javax jms lt  groupId gt                   lt artifactId gt jms lt  artifactId gt               lt  exclusion gt           lt  exclusions gt       lt  dependency gt

User · Answer

Try forcing updates using the mvn cpu option   usage  mvn  options    lt goal s  gt     lt phase s  gt    Options   -cpu --check-plugin-updates            Force upToDate check for any                                         relevant registered plugins

User · Answer

Another solution if you don t want to modify your settings   Download jms-1 1 jar from JBoss repository then   mvn install install-file -DgroupId javax jms -DartifactId jms -Dversion 1 1 -Dpackaging jar -Dfile jms-1 1 jar

User · Answer

May not be the exactly same problem  but there is a nice article on the same line Here

User · Answer

A check of ibliblio and java net repositories reveal that jmx related jar is not present in either  I think you should manually download jms and install them locally as discussed here

User · Answer

I also faced the same issue when I started using following maven dependency version for log4j  1 2 15  in my project    lt dependency gt     lt groupId gt log4j lt  groupId gt     lt artifactId gt log4j lt  artifactId gt     lt version gt 1 2 15 lt  version gt   lt  dependency gt    Following error was thrown at me    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 - gt   Help 1    I started using following log4j  1 2 17  version and it helped me solve this issue without any configurations related fixes     lt dependency gt         lt groupId gt log4j lt  groupId gt         lt artifactId gt log4j lt  artifactId gt         lt version gt 1 2 17 lt  version gt       lt  dependency gt

User · Answer

Log4 version 1 2 17 automatically resolves the issue as it has depency on geronimo-jms  I got the same issue with log4j- 1 2 15 version     Added with more around the issue    using 1 2 17 resolved the issue during the compile time but the server Karaf  was using 1 2 15 version thus creating conflict at run time  Thus I had to switch back to 1 2 15    The JMS and JMX api were available for me at the runtime thus i did not import the J2ee api   what i did was I used the compile time dependency on 1 2 17 but removed it at the runtime                lt dependency gt               lt groupId gt log4j lt  groupId gt               lt artifactId gt log4j lt  artifactId gt               lt version gt 1 2 17 lt  version gt           lt  dependency gt            lt build gt           lt plugins gt               lt plugin gt                   lt groupId gt org apache felix lt  groupId gt                   lt artifactId gt maven-bundle-plugin lt  artifactId gt                   lt extensions gt true lt  extensions gt                   lt configuration gt                       lt instructions gt                           lt Bundle-SymbolicName gt   project groupId    project artifactId  lt  Bundle-SymbolicName gt                                                             lt Import-Package gt  org apache log4j     lt  Import-Package gt

User · Answer

In fact the real solution for this issue is to use the jms-api-1 1-rev-1 jar artifact available on Maven Central   http   search maven org  artifactdetails 7Cjavax jms 7Cjms-api 7C1 1-rev-1 7Cjar

User · Answer

You import one dependency  and this dependency is dependent on com sun jmx jmxri jar 1 2 1 and others  but com sun jmx jmxri jar 1 2 1 cannot be found in central repository   so you d better try to import another version   Here suppose your dependency may be log4j  and you can try to import log4j log4j jar 1 2 13

[maven-2] The following artifacts could not be resolved: javax.jms:jms:jar:1.1

Examples related to maven-2

Examples related to jar

Examples related to sun