The Maven Archiver is mainly used by plugins to handle packaging. The version
numbers referenced in the Since column on this page are the version of the
Maven Archiver component – not for any specific plugin. To see which version of
Maven Archiver a plugin uses, go to the site for that plugin.
You should specify the version in your project’s dependency configuration:
The Maven Plugin Tools contains the necessary tools to generate
rebarbative content like descriptor, help and documentation. In addition,
it provides tools to write Maven Plugins in scripting languages like Ant
The Maven Plugin Plugin is used to create a Maven plugin descriptor for
any Mojo’s found in the source tree, to include in the JAR. It is also
used to generate report files for the Mojos as well as for updating the
plugin registry, the artifact metadata and generating a generic help goal.
The Apache Maven team is pleased to announce the release of the Apache
Apache Maven is a software project management and comprehension tool. Based
on the concept of a project object model (POM), Maven can manage a
project’s build, reporting and documentation from a central piece of
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-shade-plugin:2.1:shade (default) on project cores-batch: Error creating shaded jar: invalid LOC header (bad signature) -> [Help 1]
.... (remove many lines for brevity).
Caused by: java.util.zip.ZipException: invalid LOC header (bad signature)
at java.util.zip.ZipFile.read(Native Method)
How could that happen? Most of the time these are downloading/network issues
which are causing something like this. In extreme rare cases it might also be a
hardware error (But usually I have my doubts about that). This means the
downloaded artifacts are not correctly downloaded or downloaded from
repositories which do not exist anymore. Or any other strange thing you could
imagine. If you have artifacts which contain html snippets this is an indicator
that you are trying to download artifacts from repositories which do not exist
anymore. This means you have to check you configuration for your used
repositories which is obviously wrong.
So now the question is: What can you do to prevent that in the furture?
If you take a look on Stackoverflow related to that. More or less all answers
will tell you to delete your local cache $HOME/.m2/repositoy and rebuild.
This is unfortunately only a try to fix a symptom but not the real cause. So
work begins with deleting the locale cache as a first step.
And now the very important part:
You have to configure Maven to check the checksums of the downloaded artifacts and
fail your build if they are not correct. This is called checksum policy which
I strongly recommend to use.
This means you have to change the configuration in your settings.xml. This means you have
to change the checksum policy in your settings.xml.
A temporary solution would be to call maven with: --strict-checksums which exactly does this
but only for the appropriate call of Maven and not always. So it is better to configure
this into your settings.xml which will look like this:
Furthermore you have to configure this for all of your repositories in your
settings.xml. If you are using a repository manager either locally or within
a corporate environment. You have to check your repository manager as well if it
is correctly configured to check the checksums. You should of course not forget
to check if you are downloading via https:// instead of http:// from all
of your remote repositories.