I needed to add an additional Maven dependency: <dependency> <groupId>org.springframework.security</groupId> <artifactId>spring-security-config</artifactId> <version>3.0.1.RELEASE</version> </dependency>
In Maven: The Definitive Guide, I wrote about the differences between Maven and Ant in the introduction the section title is “The Differences Between Ant and Maven”. Here’s an answer that is a combination of the info in that introduction with some additional notes. A Simple Comparison I’m only showing you this to illustrate the … Read more
I am sure m2eclipse Maven plugin for Eclipse – the other way around – can do that. You can configure it to download both the source files and javadoc automatically for you. This is achieved by going into Window > Preferences > Maven and checking the “Download Artifact Sources” and “Download Artifact JavaDoc” options.
The following works for me when disabling Findbugs in a child POM: <plugin> <groupId>org.codehaus.mojo</groupId> <artifactId>findbugs-maven-plugin</artifactId> <executions> <execution> <id>ID_AS_IN_PARENT</id> <!– id is necessary sometimes –> <phase>none</phase> </execution> </executions> </plugin> Note: the full definition of the Findbugs plugin is in our parent/super POM, so it’ll inherit the version and so-on. In Maven 3, you’ll need to use: … Read more
I want to import existing maven project into eclipse. I found 2 ways to do it, one is through running from command line mvn eclipse:eclipse and another is to install maven eclipse plugin from eclipse. What is the difference between the both and which one is preferable? The maven-eclipse-plugin is a Maven plugin and has … Read more
You should not need to access Maven-specific files to get the version information of any given library/class. You can simply use getClass().getPackage().getImplementationVersion() to get the version information that is stored in a .jar-files MANIFEST.MF. Luckily Maven is smart enough Unfortunately Maven does not write the correct information to the manifest as well by default! Instead … Read more
Maven 3 (as of beta 1) now supports parallel builds as an experimental feature. For example, mvn -T 4 clean install # Builds with 4 threads mvn -T 1C clean install # 1 thread per cpu core mvn -T 1.5C clean install # 1.5 thread per cpu core Full documentation can be found on the … Read more
The Maven build lifecycle now includes the “integration-test” phase for running integration tests, which are run separately from the unit tests run during the “test” phase. It runs after “package”, so if you run “mvn verify”, “mvn install”, or “mvn deploy”, integration tests will be run along the way. By default, integration-test runs test classes … Read more
The Maven Versions plugin and it’s display-dependency-updates mojo are what you’re looking for: mvn versions:display-dependency-updates Here is what the output looks like: [INFO] ———————————————————————— [INFO] Building Build Helper Maven Plugin [INFO] task-segment: [versions:display-dependency-updates] [INFO] ———————————————————————— [INFO] [versions:display-dependency-updates] [INFO] [INFO] The following dependency updates are available: [INFO] org.apache.maven:maven-artifact …………………… 2.0 -> 2.0.9 [INFO] org.apache.maven:maven-plugin-api …………………. 2.0 … Read more
I recommend using type instead of classifier (see also: classifier). It tells Maven a bit more explicitly what you are doing (and I’ve found that m2eclipse and q4e both like it better). <dependency> <groupId>com.myco.app</groupId> <artifactId>foo</artifactId> <version>1.0-SNAPSHOT</version> <type>test-jar</type> <scope>test</scope> </dependency>