Invalid or corrupt jarfile xxx.jar

I. Problems encountered

The feature of Artifacts packaging is that a large number of jar packages will be generated in the directory, and each dependent package exists independently, and only the development package can be replaced when updating.

The package that I have been using Artifacts to type before will generate the MANIFEST.MF file. Later, "Invalid or corrupt jarfile xxx.jar" always appears, and it can be successful once or twice, which is very distressing.

Second, the solution

Use mav install instead to package, which can solve the above problems.The feature is that all dependent packages will be packaged into a jar package, so the jar will be relatively large, ranging from tens of megabytes to 100 or 200 megabytes.

I have a new problem.The jar can be generated, but it prompts that a jar does not exist during execution.

I know this jar package, it is a private package, it is not in the maven repository, it is accessed in the form of systemPath.

Three, import maven local library

The web is a good thing, and a solution has been found.Import the private jar package into the maven local repository.The command is as follows:

mvn install:install-file -Dfile=xxx\xxx.jar -DgroupId=xxx -DartifactId=xxx -Dversion=x.x.x -Dpackage=jar

Dfile, refers to the original location of the jar

DgroupId, give the package a group name, that is, the package path

DartifactId, refers to the product name, that is, the name of the jar

Dversion, version number, ordinary strings can also be used

Dpackage, package type, fixed jar