Maven on Erwähnenswert

maven central release with github in 30 seconds

Wed, 21 Sep 2016 14:23:07 +0100

As a passionate developer I always strive to optimise my build chain for speed and simplicity. In this example I’d like to publish a library on maven central without any onsite build tooling except my IDE. So lets see how to get rid of gpg key management and implement a trivial push-button release process with Github and TravisCI.

(This is reblogged originally from idealo/logback-redis/wiki/Release-Process and sponsored by [Idealo] https:/www.idealo.de)

List the classpath with guava

Tue, 13 Oct 2015 21:23:07 +0000

I wanna use some resources on my classpath and dont know the exact path to address them. I’ll show this using an example with jquery.

I have dependency and want to use the jquery inside.

<project ...>
 ...
 <dependencies>
 ...
 <dependency>
 <groupId>org.webjars</groupId>
 <artifactId>jquery</artifactId>
 <version>2.1.4</version>
 </dependency>
 ...
 <dependency>
 <groupId>com.google.guava</groupId>
 <artifactId>guava</artifactId>
 <version>18.0</version>
 </dependency>
 ...
 <dependency> // just for my convinience ;)
 <groupId>org.apache.commons</groupId>
 <artifactId>commons-io</artifactId>
 <version>1.3.2</version>
 </dependency>
 ...
 </dependencies>
</project>

With this demo test:

Easy distinct unit and integration test code coverage with sonarqube

Thu, 05 Feb 2015 23:23:07 +0000

Simple compute distinct code coverage for unit tests and integration tests. I used jacoco 0.7.2, sonarqube 5.0 and maven 3.2.5 to cook the numbers ;).

<project ...>
 ...
 <profile>
 <id>sonar-coverage</id>
 <build>
 <plugins>
 <plugin>
 <groupId>org.jacoco</groupId>
 <artifactId>jacoco-maven-plugin</artifactId>
 <version>0.7.2.201409121644</version>
 <configuration>
 <append>true</append>
 </configuration>
 <executions>
 <execution>
 <id>agent-for-ut</id>
 <goals>
 <goal>prepare-agent</goal>
 </goals>
 </execution>
 <execution>
 <id>agent-for-it</id>
 <goals>
 <goal>prepare-agent-integration</goal>
 </goals>
 </execution>
 <execution>
 <id>jacoco-site</id>
 <phase>post-integration-test</phase>
 <goals>
 <goal>report</goal>
 </goals>
 </execution>
 </executions>
 </plugin>
 </plugins>
 </build>
 </profile>
 ...
</project>

A simple call with maven to run the test suite and activate jacoco class instrumentation would be:

lint-maven-plugin - check your pom.xml

Mon, 09 Sep 2013 14:00:02 +0000

We know for each and everything there are some Do’s and many Don’ts. This is about recommendations on your pom.xml of your maven project.

Just try this:

$ mvn com.lewisd:lint-maven-plugin:check
[INFO] Scanning for projects...
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Maven POM lint plugin 0.0.9-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- lint-maven-plugin:0.0.8:check (default-cli) @ lint-maven-plugin ---
[INFO] Writing summary report
[INFO] [LINT] Completed with 3 violations
[INFO] [LINT] OSSIssueManagementSectionRule: missing section : 0:0 : /home/lars/development/workspaces/sonar/lint-maven-plugin/pom.xml
[INFO] [LINT] ExecutionId: Executions must specify an id : 346:40 : /home/lars/development/workspaces/sonar/lint-maven-plugin/pom.xml
[INFO] [LINT] OSSContinuousIntegrationManagementSectionRule: missing section : 0:0 : /home/lars/development/workspaces/sonar/lint-maven-plugin/pom.xml
[INFO] Writing xml report
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 2.678s
[INFO] Finished at: Mon Sep 09 02:00:32 CEST 2013
[INFO] Final Memory: 11M/267M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal com.lewisd:lint-maven-plugin:0.0.8:check (default-cli) on project lint-maven-plugin: [LINT] Violations found. For more details, see error messages above, or results in /home/lars/development/workspaces/sonar/lint-maven-plugin/target/maven-lint-result.xml -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException

List of rules Link to heading

You can see the list of supported rules with: