maven-wrapper | updated version of this project take | Build Tool library

Sometimes the answer is in front of us, but tired eyes can make us blind :D

As @JFabianMeier said, there is no Maven 3.7 and Maven wrapper scripts are included starting from Maven 4.0

https://maven.apache.org/plugins/maven-wrapper-plugin/

/workspace/.mvn/wrapper/maven-wrapper.properties: No such file

The error indicates that Maven is trying to open the file maven-wrapper.properties, however it is not found. Please confirm that the file is there.

You may want to take a look to https://stackoverflow.com/a/50105966/6003934

For anyone running into the same problem, my mistake was that I assumed the classpath to be correct, but it wasn't. It seems the logs don't take into account the value of the classpath environment variable, and in my computer that variable had a value, when it shouldn't be set. Unsetting it with set classpath= solved the classpath issues that were causing the error with pitest.

It looks like you have a mvnw file in the root of your project directory but are missing other files required by Maven wrapper. Those usually reside in the .mvn/wrapper directory of your application. You might have deleted them.

You have two options:

1. Delete the other files for Maven Wrapper as well: mvnw and mvnw.cmd
2. Reinstall the missing files for Maven Wrapper: mvn -N io.takari:maven:0.7.7:wrapper

I'd go for option 2. Using the wrapper is generally preferred to ensure your project is run with the Maven version you expect.

Basically, these "includes" (negated excludes) make sure directories beneath src/main and src/test that may be named target, for example, a package name, are not missed in a commit.

Per a discussion on the Spring Initializr gitter, Andy Wilkinson, a Spring committer, noted:

It's to prevent the ignore for Maven's build output directory (target) from causing code in a package named target from being ignored.

In many cases, safely deleted in individual use cases, "unless you work for Target" (Target Brands, Inc. might have packages namespaced as com.target.api.*) (h/t to Andy for the example).

My question should have been answered in the use of src/main and src/test, but I let the misdirection of the word, target, confuse me. In fact, I was demonstrating this in my own example, but couldn't get past the word. D'oh!

Step 1 - Verify Java Installation on your Machine Open console and execute the following java command.

OS Task Command -Windows Open Command Console c:> java -version -Linux Open Command Terminal $ java -version -Mac Open Terminal machine:~ joseph$ java -version Let's verify the output for all the operating systems −

If you do not have Java installed, install the Java Software Development Kit (SDK) from https://www.oracle.com/technetwork/java/javase/downloads/index.html. We are assuming Java 1.7.0.60 as installed version for this tutorial.

Step 2 - Set JAVA Environment Set the JAVA_HOME environment variable to point to the base directory location where Java is installed on your machine. For example −

OS Output Windows Set the environment variable JAVA_HOME to C:\Program Files\Java\jdk1.7.0_60 Linux export JAVA_HOME=/usr/local/java-current Mac export JAVA_HOME=/Library/Java/Home Append Java compiler location to System Path.

Verify Java Installation using java -version command as explained above.

Step 3 - Download Maven Archive Download Maven 2.2.1 from https://maven.apache.org/download.cgi.

OS Archive name Windows apache-maven-3.3.1-bin.zip Linux apache-maven-3.3.1-bin.tar.gz

Step 4 - Extract the Maven Archive Extract the archive, to the directory you wish to install Maven 3.3.1. The subdirectory apache-maven-3.3.1 will be created from the archive.

OS Location (can be different based on your installation) Windows C:\Program Files\Apache Software Foundation\apache-maven-3.3.1 Linux /usr/local/apache-maven

Step 5 - Set Maven Environment Variables Add M2_HOME, M2, MAVEN_OPTS to environment variables.

OS Output Windows Set the environment variables using system properties.

M2_HOME=C:\Program Files\Apache Software Foundation\apache-maven-3.3.1 M2=%M2_HOME%\bin MAVEN_OPTS=-Xms256m -Xmx512m

Linux
Open command terminal and set environment variables.

export M2_HOME=/usr/local/apache-maven/apache-maven-3.3.1 export M2=$M2_HOME/bin

export MAVEN_OPTS=-Xms256m -Xmx512m

export M2=$M2_HOME/bin

export MAVEN_OPTS=-Xms256m -Xmx512m

Step 6 - Add Maven bin Directory Location to System Path Now append M2 variable to System Path.

OS Output Windows Append the string ;%M2% to the end of the system variable, Path. Linux export PATH=$M2:$PATH Mac export PATH=$M2:$PATH

Step 7 - Verify Maven Installation Now open console and execute the following mvn command.

OS Task Command Windows Open Command Console c:> mvn --version Linux Open Command Terminal $ mvn --version

Finally, verify the output of the above commands, which should be as follows −

What you have done in your .gitignore is correct. You need to remove the files from the staging area by doing a git rm -r --cached and then commit the changes. When there will be any changes in the files next time, they won't cause trouble :)

You might want to refer to this as well.

Best

If you already made a copy of the jar to the container why do you try to compile the project again?

I thik that you could simply just run the jar file with CMD.

But if you want to the container to compile the project just copy the source files, compile and run the jar.

trye something like that:

I followed this https://spring.io/blog/2018/11/08/spring-boot-in-a-container to dockerize the app with my application.properties looking like this: