Page tree
Skip to end of metadata
Go to start of metadata

Noteworthy

This version introduces a couples of fixes related to Clover and annotation processing tools (for code generation), and a few other goodies:

  • Building test-jars is now easier, no need to copy and paste some obscure xml snippet. To generate a test-jar for your module, set the <skipTestJar> property to false. See BUILD-194 - Getting issue details... STATUS . Note: in a future version of the parent poms, we might actually switch to generating them by default (which would at least rid us of this odd double-negative to enable the feature.) See  BUILD-212 - Getting issue details... STATUS .
  • We're now using Animal Sniffer , which guarantees we're not accidentally using APIs that don't use in the JDK targetted by <javaVersion>. See  BUILD-198 - Getting issue details... STATUS .
  • You can use Asciidoc to write Javadoc ! Get rid of the pesky HTML in your Javadoc: it's not readable and pretty in the source as well as in the generated Javadoc html. To enable it, set <javadocDoclet>${asciidocDoclet}</javadocDoclet> in your pom's properties. See  BUILD-200 - Getting issue details... STATUS .
  • The current project's version number as well as the JDK version set by <javaVersion> are available as "parsed" versions for other plugins and resource filtering. See  BUILD-201 - Getting issue details... STATUS .

Upgrading

Upgrading should be straightforward. Please upgrade at your earliest convenience, ideally before your next release.

Take care of the following:

  • If you're using annotation processing tools (for code generation), you might still see some side-effects due to the maven-compiler-plugin update, and potential issues with Clover:  BUILD-211 - Getting issue details... STATUS .

The following workarounds can be removed:

  • Downgrade of the dependency plugin because dependency:analyze did not work with 2.10. We now use 2.11, so you can remove the snippet that downgraded it to 2.9 in your project. See  BUILD-199 - Getting issue details... STATUS
  • Skipping clover for a single submodule (or in general) is now done through a simple <skipClover> property. You can remove snippets that reconfigured Clover, as well as the removal of enable-clover in <additionalReleaseProfiles>. See  BUILD-124 - Getting issue details... STATUS .

Complete changelog

See https://jira.magnolia-cms.com/jira/secure/ReleaseNote.jspa?projectId=10330&version=15952

 

 

  • No labels