M1 means Milestone 1, it’s a release name, like beta or alpha. RC means Release Candidate. A milestone means that the application got a huge improvement from the todo list. A release candidate is a release that can be the final release unless some major bugs are found. To quote the ASF: Releases that only … Read more
According to the documentation on the Maven Surefire Plugin, -Dmaven.test.skip should skip both compilation and execution of the tests. By contrast, -DskipTests just skips the test execution: the tests are still compiled.
Use the following in the configuration of the maven-assembly-plugin: <configuration> <finalName>custom-name</finalName> <appendAssemblyId>false</appendAssemblyId> </configuration> Full details in the official documentation of the assembly:single mojo.
The environment variable to set is MAVEN_OPTS, for example MAVEN_OPTS=-Xmx1024m. The maxmem configuration in the pom only applies when you set the compiler plugin to fork javac into a new JVM. Otherwise the plugin runs inside the same VM as Maven and thus within the memory passed on the command line via the MAVEN_OPTS. To … Read more
I have a doubt about what you are trying to do but but I’ll assume you want to reuse the tests that you have created for a project (module1) in another. As explained in the note at the bottom of the Guide to using attached tests: Note that previous editions of this guide suggested to … Read more
I had to specify different generateDirectory (without this, the plugin was considering that files were up to date and wasn’t generating anything during the second execution). And I recommend to follow the target/generated-sources/<tool> convention for generated sources so that they will be imported in your favorite IDE automatically. I also recommend to declare several execution … Read more
Perhaps a version of maven war plugin is being used, which does not work with Java 7? As per this issue (which describes a similar problem), 2.1.1 version of maven war plugin should work. Include the following in your pom.xml <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-war-plugin</artifactId> <version>2.1.1</version> </plugin>
Not possible. Maven checks the repositories in their declaration order until a given artifact gets resolved (or not). Some repository manager can do something approaching this though. For example, Nexus has a routes feature that does something equivalent.
You need to indicate the groupId, the artifactId and the version for your artifact: mvn install:install-file \ -DgroupId=javax.transaction \ -DartifactId=jta \ -Dpackaging=jar \ -Dversion=1.0.1B \ -Dfile=jta-1.0.1B.jar \ -DgeneratePom=true
If you want just the local repo, try this: mvn help:evaluate -Dexpression=settings.localRepository | grep -v ‘\[INFO\]’ EDIT I’m revisiting this after years because recent versions of the Maven help plugin introduced a useful parameter for the evaluate goal called forceStdout that allows us to remove the need to grep the output: mvn help:evaluate -Dexpression=settings.localRepository -q … Read more