Log4j 1.2.15 JMS Maven m2eclipse issue and Solution

Jar hell III: the issue and solution of log4j 1.2.15 in m2eclipse
　　

The version 1.3 of log4j is still in the Alibaba Cloud version. Version 1.2 is up to version 1.2.15, but maven2 has an issue in eclipse.

After installing Maven clean, the maven package will build failure, with the following warning information:
[Warning] invalid Pom for javax. JMS: jar: 1.1, transitive dependencies (if any) will not be available, enable debug logging for more details
[Warning] invalid Pom for com. Sun. Jdmk: jmxtools: jar: 1.2.1, transitive dependencies (if any) will not be available, enable debug logging for more details
[Warning] invalid Pom for com. Sun. JMX: jmxri: jar: 1.2.1, transitive dependencies (if any) will not be available, enable debug logging for more details
　　

These loss jar files are empty in the repository, and their pom. xml example files do not have their jar files. Instead, you can build success only after you use the Eclipse project/clean and then upload the maven package. But back to version 1.2.14, there is no such problem. It was only after dependency graph that log4j 1.2.15 relied on the preceding three jar files.

Why is package okay after project/clean? No! No solution. It may be caused by the reliance on the subject!
2010/3/11. Then, find the solution that references 1.2.15. The dependency settings are as follows:

Log4j
Log4j
1.2.15

Javax. JMS
JMS

Com. Sun. Jdmk
Jmxtools

Com. Sun. JMX
Jmxri

Javax. Mail
Mail

　　

Maven package 1.2.15 can be referenced by the exclusion method.

<Dependency>
<Groupid> log4j </groupid>
<Artifactid> log4j </artifactid>
<Version> 1.2.15 </version>
<Exclusions>
<Exclusion>
<Groupid> javax. JMS </groupid>
<Artifactid> JMS </artifactid>
</Exclusion>
<Exclusion>
<Groupid> com. Sun. Jdmk </groupid>
<Artifactid> jmxtools </artifactid>
</Exclusion>
<Exclusion>
<Groupid> com. Sun. JMX </groupid>
<Artifactid> jmxri </artifactid>
</Exclusion>
<Exclusion>
<Groupid> javax. Mail </groupid>
<Artifactid> mail </artifactid>
</Exclusion>
</Exclusions>
</Dependency>

 

It is disgusting that if the dependent component is declared in the parent pom, the Child Project will inherit the dependency, but will not inherit the exclusion attribute !!

I don't know if it's a Maven bug or why I didn't read the manual well.

 

Complain about the Nexus (version nexus-oss-webapp-1.7.2) This player is also a bug, through the interface to configure the time, do not move CPU 100%

The new version of Nexus (1.8) has the jetty null problem, such as the real FK and the m2eclipse. If you do not know the dependency, a bunch of third-party plug-ins have been installed.

You cannot use it, or you have encountered complicated dependency errors when installing third-party plug-ins!

 

 

2010/5/12 without charge: Version 1.2.16 does not have this situation. ---> 1.2.16 I don't know why the maven repository only has pom.