Maven Learning Notes (iii)

Sometimes we may need to package an executable jar package in the project, I also recently met, very silly and naïve to use the following configuration:

< Packaging >jar</packaging>

As always, the effect is good, packaging success, a implementation, dumbfounded, the JVM is very rude throws an exception: XXX does not have a master list exception. Online search information, a large pile of programs:

 <plugin>    <groupId>Org.apache.maven.plugins</groupId>    <Artifactid>Maven-jar-plugin</Artifactid>    <Configuration>        <Archive>            <Manifest>                                            <MainClass>"Entry Path"</MainClass>            </Manifest>        </Archive>    </Configuration></plugin>

Specify MainClass can, and fart on the top of the package execution, incredibly wrong, can't find a dependency. In general, this is possible, but my scene is relatively complex, the current project also relies on some other dependent packages, need to be packaged with these dependent files are also packaged in, Maven in the jar packaging, generally do not package dependencies, the solution is as follows:

To be Continued ...

Done, make a record, for follow-up inspection.

Maven Learning Notes (iii)