# In the implementation of packaged mvn Clean Assembly: Assembly # above error ------------------------------ [INFO] Total Time: 2.872 S [the INFO] Finished AT: 2019-08-08T13: 44 is: 10 + 08: 00 [the INFO] Final Memory: 13M / 168M [the INFO] --------------- -------------------------------------------------- ------- [ERROR] Failed to execute goal on project FlinkTest: Could not resolve dependencies for project com.badou:FlinkTest: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. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
From the error term, due to the lack of results in some packages, after a search found to be caused due log4j version, use the version 1.2.15 When packing, be found to rise to 1.2.16 does not work, but the upgrade to 1.2 .17 do not have this problem.
1.2.17 is replaced by a solution. You also can find the corresponding jar into the repository. The last approach is to directly commented on the log4j package when this is possible.