Deleting full .m2/repository local repository solved my problem. Or else you need to know what plugins are you using exactly with their dependencies as one of the plugin suffered a problem while downloading.
I had a very similar problem; when I included a signed JAR (bouncycastle) in the project. Its signature was repackaged verbatim, resulting in an obvious SecurityException: java.lang.SecurityException: Invalid signature file digest for Manifest main attributes Filtering of all sorts failed; the solution that works for me looks like this in the pom.xml: <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-dependency-plugin</artifactId> … Read more
clean is its own build lifecycle phase (which can be thought of as an action or task) in Maven. mvn clean install tells Maven to do the clean phase in each module before running the install phase for each module. What this does is clear any compiled files you have, making sure that you’re really … Read more
Could not transfer artifact org.apache.maven.plugins:maven-dependency-plugin:pom:2.8 from/to central (http://repo.maven.apache.org/maven2): repo.maven.apache.org: Unknown host repo.maven.apache.org It seems like your maven cannot access remote central repository. Check if you have an established internet connection. Check if you can access default maven repo http://repo.maven.apache.org/maven2 in your browser. Check if you have correct configuration in <repositories> and <proxies> in your your … Read more
Alternatively, I recommend installing Homebrew for these kinds of utilities. Then you just install Maven using: brew install maven PS: If you got a 404 error, try doing a brew update just before
You should not access test classes from your application code, but rather create a main (the same main) in the test scope and create an additional artifact for your project. However, in this additional artifact (jar) you would need to have: The test classes The application code classes External dependencies required by application code (in … Read more
The <uniqueVersion> configuration applied to artifacts that were deployed (via mvn deploy) to a Maven repository such as Nexus. To remove these from Nexus, you can easily create an automated job to purge the SNAPSHOT repository every day. It can be configured to retain a certain number of shapshots or keep them for a certain … Read more
I found a solution to do this by inspecting the commit in the Maven git repository that is responsible for the default HTTP blocking: https://github.com/apache/maven/commit/907d53ad3264718f66ff15e1363d76b07dd0c05f My solution is as follows: In the Maven settings (located in ${maven.home}/conf/settings.xml or ${user.home}/.m2/settings.xml), the following entry must be removed: <mirror> <id>maven-default-http-blocker</id> <mirrorOf>external:http:*</mirrorOf> <name>Pseudo repository to mirror external repositories initially … Read more
Check how your maven-compiler-plugin is configured, it should use java version 7 or higher: <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-compiler-plugin</artifactId> <version>3.1</version> <configuration> <source>1.7</source> <target>1.7</target> </configuration> </plugin> For a more complete answer see the one below.
Look in your settings.xml (or, possibly your project’s parent or corporate parent POM) for the <repositories> element. It will look something like the below. <repositories> <repository> <id>central</id> <url>http://gotoNexus</url> <snapshots> <enabled>true</enabled> <updatePolicy>always</updatePolicy> </snapshots> <releases> <enabled>true</enabled> <updatePolicy>daily</updatePolicy> </releases> </repository> </repositories> Note the <updatePolicy> element. The example tells Maven to contact the remote repo (Nexus in my case, … Read more