I was able to solve this by downgrading Spring Boot: <dependency> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-starter-web</artifactId> <version>2.3.3.RELEASE</version> </dependency> Guess it’s just not compatible with 2.4.0 yet. Specifically I also had to ensure that I used 2.3.3.RELEASE and not anything more recent due to other issues I ran across.
Some plugins, like surefire, let you set them. There’s no way, in general, in the pom. The doc for surefire is is here. Surefire will set environment variables for the duration of the run of the tests, not for anything else. And you have to make surefire fork. In the configuration … <configuration> <forkMode>always</forkMode> <environmentVariables> … Read more
I had a similar problem while I was trying to start my tomcat. I would suggest that you check “Classpath” the following way: 1) Run Configurations Right click on your project then click “Run” -> “Run Configurations…” there check your settings for you project (e. g. in my case it was the Apache Tomcat) here … Read more
Your presumption is correct, the top level project being pom packaging should have no source. So start by removing (just delete or move elsewhere) the src folder from the top level (and everything under it… main, java, resources, text…) Now, looking at your modules, they look correct. You can test they are configured properly by … Read more
You are correct that the artifactId helps identify the project. The name is simply a human-readable “friendly” name. It is not required for a basic setup. From the Maven documentation, artifactId: The artifactId is generally the name that the project is known by. Although the groupId is important, people within the group will rarely mention … Read more
You have to surround the plugins tag with the build tag like this: <build> <plugins> <plugin> … </plugin> </plugins> </build> or with the build and pluginManagement tags like this: <build> <pluginManagement> <plugins> <plugin> … </plugin> </plugins> </pluginManagement> </build>
It’s a bug in the Eclipse Maven support. Eclipse doesn’t support all of the global Maven properties as per the Maven specs. According to the specs: ${java.home} specifies the path to the current JRE_HOME environment use with relative paths to get for example At least in Eclipse 4.3.1 that is not the case, here java.home … Read more
Maven allows you to define properties in the project’s POM. You can do this using a POM file similar to the following: <project> … <properties> <server.url>http://localhost:8080/manager/html</server.url> </properties> … <build> <plugins> <plugin> … <configuration> <url>${server.url}</url> <server>tomcat</server> </configuration> … </plugin> </plugins> </build> </project> You can avoid specifying the property within the properties tag, and pass the value … Read more
Since version 2.10 of the Versions Maven Plugin you can simply do: mvn versions:set -DremoveSnapshot
JBoss have started synchronising their own repo with Maven central as posted on the JBoss community blog , therefore hibernate artifacts are now available without the need to add the JBoss repository to your pom.xml or repository manager. Search result for hibernate-core: To add the Hibernate Core 3.6.3 to your project, just add the following … Read more