Actually, all 3 are Maven repository. We use these maven repositories to our build by using its URL address or its location in the local file system. By using URL: repositories { maven { url(“https://plugins.gradle.org/m2/”) } } By using local file system: repositories { maven { url ‘../maven-repo’ } } Gradle has three “aliases” which … Read more
After some research and trials on how to get the Maven project version in a SpringBoot application I couldn’t find anything working for me. Using a manifest is definitively a rotten path due to class loaders issues, i.e. one gets the first manifest Spring finds, which in my case was not the one of my … Read more
This solved my issue. It was 2.10 in my POM, just updated to 2.19.1 and refresh the POM Add to your pom : <plugins> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-surefire-plugin</artifactId> <version>2.19.1</version> </plugin> </plugins> In your error code he didn’t find surefire plugin so add it
It would be helpful if you can provide a code snippet of your maven-war-plugin. Looks like the web.xml is at right place, still you can try and give the location explicitly <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-war-plugin</artifactId> <configuration> <webXml>src\main\webapp\WEB-INF\web.xml</webXml> </configuration> </plugin>
Add a <version> element after the <plugin> <artifactId> in your pom.xml file. Find the following text: <plugin> <artifactId>maven-compiler-plugin</artifactId> Add the version tag to it: <plugin> <artifactId>maven-compiler-plugin</artifactId> <version>2.3.2</version> The warning should be resolved. Regarding this: ‘build.plugins.plugin.version’ for org.apache.maven.plugins:maven-compiler-plugin is missing Many people have mentioned why the issue is happening, but fail to suggest a fix. All … Read more
When you start up Maven from the command line, it goes through a number of stages. Here is a pseudo description of these stages, I am intentionally simplifying the exact sequencing (with the risk of saying things that are slightly incorrect/out-of-order) so that you can see why what you are trying to do cannot work. … Read more
Maven does not allow cyclic dependencies between projects, because otherwise it is not clear which project to build first. So you need to get rid of this cycle. One solution is the one you already mentioned, to create another project. Another one would be to just move some classes from B to C or vice … Read more
I had the same error. In my case I am using Netbeans 7.1.2, I am posting this because maybe someone end up here same as I did. I tried to configure the proxy options from the GUI, but the documentation says that maven doesn’t read those. So I checked the NetBeans FAQ here : What … Read more
Probably, contents of the JAR files in your local .m2 repository are HTML saying “301 Moved Permanently”. It seems that mvn does not handle “301 Moved Permanently” properly as expected. In such a case, download the JAR files manually from somewhere (the central repository, for example) and put them into your .m2 repository. See also: … Read more
I have the same problem as you and found out that change from servlet-api to javax.servlet.api will fix the problem. Hope this help. Please note that, I am using Juno Eclipse, Tomcat 7, Dynamic Web Module 3.0, and JDK 1.7. <dependency> <groupId>com.sun.faces</groupId> <artifactId>jsf-api</artifactId> <version>2.1.13</version> </dependency> <dependency> <groupId>com.sun.faces</groupId> <artifactId>jsf-impl</artifactId> <version>2.1.13</version> </dependency> <dependency> <groupId>javax.servlet</groupId> <artifactId>javax.servlet-api</artifactId> <version>3.0.1</version> </dependency>