Weirdness is highly subjective, I just suggest to follow the official recommendation: Guide to naming conventions on groupId, artifactId and version groupId will identify your project uniquely across all projects, so we need to enforce a naming schema. It has to follow the package name rules, what means that has to be at least as … Read more
If you want to only download dependencies without doing anything else, then it’s: mvn dependency:resolve Or to download a single dependency: mvn dependency:get -Dartifact=groupId:artifactId:version If you need to download from a specific repository, you can specify that with -DrepoUrl=…
Start maven with -X option (debug) and examine the beginning of the output. There should be something like this: … [INFO] Error stacktraces are turned on. [DEBUG] Reading global settings from c:\….\apache-maven-3.0.3\conf\settings.xml [DEBUG] Reading user settings from c:\….\.m2\settings.xml [DEBUG] Using local repository at C:\….\repository … (Original directory names are removed by me)
You can do this using the maven-assembly plugin with the “jar-with-dependencies” descriptor. Here’s the relevant chunk from one of our pom.xml’s that does this: <build> <plugins> <!– any other plugins –> <plugin> <artifactId>maven-assembly-plugin</artifactId> <executions> <execution> <phase>package</phase> <goals> <goal>single</goal> </goals> </execution> </executions> <configuration> <descriptorRefs> <descriptorRef>jar-with-dependencies</descriptorRef> </descriptorRefs> </configuration> </plugin> </plugins> </build>
OK, I have found the problem. I use some reporting plugins. In the documentation of the failsafe-maven-plugin I found, that the <encoding> configuration – of course – uses ${project.reporting.outputEncoding} by default. So I added the property as a child element of the project element and everything is fine now: <properties> <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding> <project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding> </properties> See also … Read more
Any best practices here? Use the Maven advanced reactor options, more specifically: -pl, –projects Build specified reactor projects instead of all projects -am, –also-make If project list is specified, also build projects required by the list So just cd into the parent P directory and run: mvn install -pl B -am And this will build … Read more
To run a single test method in Maven, you need to provide the command as: mvn test -Dtest=TestCircle#xyz test where TestCircle is the test class name and xyz is the test method. Wild card characters also work; both in the method name and class name. If you’re testing in a multi-module project, specify the module … Read more
Problems of popular approaches Most of the answers you’ll find around the internet will suggest you to either install the dependency to your local repository or specify a “system” scope in the pom and distribute the dependency with the source of your project. But both of these solutions are actually flawed. Why you shouldn’t apply … Read more
NOTE: The mentioned LATEST and RELEASE metaversions have been dropped for plugin dependencies in Maven 3 “for the sake of reproducible builds”, over 6 years ago. (They still work perfectly fine for regular dependencies.) For plugin dependencies please refer to this Maven 3 compliant solution. If you always want to use the newest version, Maven … Read more
<build> <plugins> <plugin> <artifactId>maven-assembly-plugin</artifactId> <configuration> <archive> <manifest> <mainClass>fully.qualified.MainClass</mainClass> </manifest> </archive> <descriptorRefs> <descriptorRef>jar-with-dependencies</descriptorRef> </descriptorRefs> </configuration> </plugin> </plugins> </build> and you run it with mvn clean compile assembly:single Compile goal should be added before assembly:single or otherwise the code on your own project is not included. See more details in comments. Commonly this goal is tied to … Read more