2.2.0

New Features

#43 Enhancements for unmanaged project versions:

• The option allowUnmanagedProjectVersions is now also available in the PedanticPluginConfigurationEnforcer
• The PedanticPluginConfigurationEnforcer and PedanticDependencyConfigurationEnforcer can now be configured to support other project version properties than ${project.version} by using the option allowedUnmanagedProjectVersionProperties
• The CompoundPedanticEnforcer provides the same options as follows:
  • The options allowUnmanagedProjectVersions and allowedUnmanagedProjectVersionProperties applies for dependencies and Maven plugins
  • The original option allowUnmangedProjectVersions (note the typo) will remain until version 3.x and will have the same effect as described above
  • allowUnmanagedProjectVersionsInDependencies and allowUnmanagedProjectVersionsInPlugins applies for dependencies and Maven plugins separately
  • allowedUnmanagedProjectVersionPropertiesForDependencies and allowedUnmanagedProjectVersionPropertiesForPlugins applies for dependencies and plugins separately

Thanks to @PayBas for the contribution!

Improvements

• Plugin and dependency updates

2.1.0

New Features

• #35 Add multiline support for rule configuration (Thanks @pkwarren for the contribution). Example:

  <testDependencies>
    org.assertj:assertj-core,
    org.junit.jupiter:junit-jupiter,
    org.junit.jupiter:junit-jupiter-api,
    org.junit.jupiter:junit-jupiter-engine,
    org.junit.jupiter:junit-jupiter-params
  </testDependencies>
  

• #36 Add Wildcard support for the PedanticDependencyScopeEnforcer.

Improvements

• Plugin and dependency updates
• Minor adjustments

Release 2.0.0

This is a new major release mainly because the JDK baseline was updated from JDK7 to JDK8. Projects working with lower JDK versions than 8 cannot use this version and future versions of the pedantic-pom-enforcers anymore.

New Features

• New JDK baseline: JDK8
• New enforcer rules to define an order within dependencyManagement, dependencies, pluginManagement and plugins:
  • PedanticDependencyElementEnforcer
  • PedanticPluginElementEnforcer

Improvements

• Each enforcer rule does now provide a warnOnly option which does not fail the whole build in case of a rule violation
• New default in the scopePriorities in PedanticDependencyManagementOrderEnforcer and PedanticDependencyOrderEnforcer: The import scope is now expected first. The reason is to list all BOMs (which have become more popular recently) at the beginning of the dependencyManagement section. Note: This change might be breaking if your are using import-scoped dependencies
• The default groupId org.apache.maven.plugins is now handled correctly if it is omitted for a plugin definition in the pluginManagement or the plugins section.

Release 1.3.2 (Bugfix)

When run with Java 8 the DEPENDENCY_CONFIGURATION (when manageExclusions=true) enforcer does not report dependency exclusions outside the <dependencyManagement> section. With newer Java versions the rule works correctly.
This release fixes this problem.

See Issue #23 for further details

Release 1.3.1 (Bugfix)

This release fixes a bug where POM files were not correctly paresed when using Java 9. This could lead to wrong results in some enforcer rules. See Issue #16 for more details.

If you are using Java 9, please update to this version.

Release 1.3.0

This release adds support for running on Java 9 without further configuration.