Dmytro Chyzhykov's Blog

Yet another programmer.

Skipping JaCoCo Execution Due to Missing Execution Data File

Sometimes, because of misconfiguration, JaCoCo Maven Plugin can stop working and begin notifying you about it with the following annoying message

1
2
3
4
[INFO] 
[INFO] --- jacoco-maven-plugin:0.7.1.201405082137:report (default-cli) @ project-name ---
[INFO] Skipping JaCoCo execution due to missing execution data file:/project-dir/target/jacoco.exec
[INFO] ------------------------------------------------------------------------

Let’s consider some common misconfiguration cases.

Upgrade Jersey 1.x to Use Jackson 2.x

The first new major update for Jackson since the official 1.0 release was released March 25, 2012.
But the current version (1.17.1) of Jersey 1.x still uses Jackson 1.9

If your project has REST integration tests and you sure that update is really needed and possible (there is no library in your class pass which depends strongly on Jackson 1.x), you can follow this simple and short manual to upgrade.

Running Embedded Jetty on a Random Available Port

Running Embedded Jetty on a random available port would be handful:

  • for integration testing: you can run several builds on the same continuous integration worker without port conflicts
  • for deployment: when you do not know where a particular port is taken or not
  • for development: you can run several instances of your web application just from your favourite IDE or CLI
  • for lulz