How to use POMs as a dependency in Maven?

You have to go with <dependencies> <dependency> <groupId>com.my</groupId> <artifactId>commons-deps</artifactId> <type>pom</type> </dependency> </dependencies> This will transitively add all dependencies declared in com.my:commons-deps to your current POM. Using <dependencyManagement> <dependencies> <dependency> <groupId>…</groupId> <artifactId>…</artifactId> <type>pom</type> <scope>import</scope> </dependency> </dependencies> </dependencyManagement> works as a simple ‘include’ of artifacts versions in your dependency management. Thus, it won’t add any dependency in … Read more

Maven: The packaging for this project did not assign a file to the build artifact

I don’t know if this is the answer or not but it might lead you in the right direction… (I believe these steps are for people working with Intellij IDE. The install:install is available in the Maven panel on the right by default. The below steps are alternative to it.) The command install:install is actually … Read more

What is the difference between “pom” type dependency with scope “import” and without “import”?

You can only import managed dependencies. This means you can only import other POMs into the dependencyManagement section of your project’s POM. i.e. … <dependencyManagement> <dependencies> <dependency> <groupId>other.pom.group.id</groupId> <artifactId>other-pom-artifact-id</artifactId> <version>SNAPSHOT</version> <scope>import</scope> <type>pom</type> </dependency> </dependencies> </dependencyManagement> … What then happens is that all the dependencies defined in the dependencyManagement section of the other-pom-artifact-id are included in … Read more

Spring Boot ClassNotFoundException org.springframework.core.metrics.ApplicationStartup

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.

failsafe plugin won’t run on one project but will run on another — why?

Take a look at the failsafe docs for the test names failsafe expects by default: <includes> <include>**/IT*.java</include> <include>**/*IT.java</include> <include>**/*ITCase.java</include> </includes> Are your tests named following one of these patterns? If not, try defining the <includes> element in the plugin configuration. Or change your test name(s) to fit the default pattern. Okay, now that we’ve verified … Read more