I’ve tried to start my Spring Boot Application using IntelliJ. However, I cannot seem to make it work no matter whatever solutions I tried to implement to fix it. I believe it has something to do with spring.autoconfigure package, yet the root problem remains a mystery to me. I am trying to take advantage of both Maven Multi Module System
Tag: maven
Jetty 11 Doesn’t Detect Jakarta Servlets
This is a follow up to this question. I don’t think it’s a duplicate because the accepted answer indicates that Jetty 11 doesn’t work with javax servlets, but I’m asking why Jetty 11 doesn’t work with jakarta servlets. I have an example project here that uses Jetty 9 to deploy a local server, including a javax servlet that uses the
GitLab CI docker build – docker: not found – exit code 127
I’m trying to create a CI/CD Pipeline for a simple java/maven project. The runner that I’m using is a docker runner. I’m using a dockerfile to create a container which installs maven/java/etc.. and in this container the program should be tested. Sorry for the question but I am new to CI/CD Pipelines in GitLab. GitHub works just fine have a
VSCode Maven “X.java is not on the classpath of project Y”
Currently I have an issue with Maven is Visual Studio Code where it reports errors related to the classpath. The project structure is as following: And the pom.xml of project has: This POM only serves as ‘dummy’ in order to compile each sub project And in the pom.xml of each subproject has the following: When going to any Java source
Eclipse Spring Boot need declare Maven dependency explicitly
I have 2 development PCs, both have following specification: Windows 10 1909 64 bit Installed Oracle JDK 1.8.0_281-b09 Eclipse IDE for Java Developers 2020-12 (4.18.0) The application under development is a Spring Boot project with following Maven file: When importing the project into Eclipse, one of development PC (called PC1) cannot build with following error: On the other side PC
Setting maven build property programmatically in Java without writing a plugin?
I need to define some additional properties to be used in maven plugin configurations (pom.xml). Is this possible in a programmatic way using Java code? The exec:java goal seems to run code directly inside the maven process. Is there any way to exploit this? I need the project basedir property with forward slashes such that I can use it in
why is my maven sub dependency version for spark connector package different from others
I am trying to use a pom file from a existing project and I am getting an error “Cannot resolve org.yaml:snakeyaml:1.15” What I find out about this error is that the com.datastax.spark:spark-cassandra-connector_2.11:2.5.0 uses a couple dependencies and a couple levels down it is using snakeyaml:1.15 which is quarantined by company proxy. Is there a way to specify for a given
Quarkus Maven Plugin not building anymore
For some reason the backend of our Application does not build correctly: Error message While using mvn clean install still works mvn compile quarkus:dev -pl web does not, throwing the following error message during the build of quarkus-maven-plugin:1.11.3.Final:dev: This continues with increasing time intervals. Steps Taken I already checked if the SQL Docker Container is offline, but it started as
Can’t run Maven 3.6.3 on JDK7
According to the Maven release history, it should be possible to run any recent version of Maven (at the time of writing anyway) on JDK 7. However, when I try to do so on my Ubuntu 21.04 machine, I get an error: java.lang.UnsupportedClassVersionError: com/google/inject/Module : Unsupported major.minor version 52.0. It happens even while running mvn without any parameters in a
Why default maven uses such old versions of plugins?
I am new to Maven, and struggling to find out how does maven decide what version of a plugin (e.g. maven-compiler) to use when no version is defined in pom.xml. Using latest maven version 3.8.1. Created a hello-world java program and ran mvn compile. And it downloads following versions: maven-resources-plugin:2.6:resources (default-resources) maven-compiler-plugin:3.1:compile (default-compile) maven-compiler-plugin:3.1 was released in April 2013. Latest