Releases: basepom/duplicate-finder-maven-plugin
Releases · basepom/duplicate-finder-maven-plugin
Version 2.0.1
changed
- remove old wiki-copy from docs folder
- minor updates to integration test code
- deprecation messages for deprecated parameters
Version 2.0.0
changed
- minimum Java version is now Java 11
- fix dependencies to silence Apache Maven 3.9.x warnings
removed
quiet
option no longer does anythingincludeBootClasspath
andbootClasspathProperty
were only supported up to Java 8 and the plugin now supports only Java 11 and up, so they are deprecated and no longer do anything.
Version 1.5.1
This version is identical to 1.5.0 except that it now uses the native maven 3.x logging.
removed
Removed log4j 1.x dependency. While this was not vulnerable to the log4shell attack, it is outdated and should no longer be used.
Version 1.5.0
This version is functionally (almost) unchanged from 1.4.0 except that it is using a newer build system and is built with the JDK11 compiler for JDK8 target.
The only substantial change over 1.4.0 is an additional ignored pattern (changelog.txt, #44).
added
changed
- use github actions for CI, remove travis
- use maven wrapper
- build with JDK9+ only, still support JDK8 as runtime
- CI build with JDK 11, 14
- CI run integration tests on JDK 8, 11, 14
Version 1.4.0
added
changed
- Build with basepom 30
- use slf4j 1.7.28 (from 1.7.21)
- update plugin plugin to 3.6.0 (from 3.4)
- update groovy to 3.0.0-beta-3 (from 2.4.12)
- changed Travis Build to use OpenJDK 8 and 11
- Clarify much more what is a resource and what is considered a class. This changes a lot of things that used to be matched as classes to be matched as resources. Especially all path elements (directories, jar file folders etc.) now must match the Java identifier specification. This e.g. rejects classes in Multi-release jars that are located in
META-INF/versions/<version>
becauseMETA-INF
or the version number are not valid Java identifiers. An exception is made forpackage-info
andmodule-info
class files, whose names are not valid Java identifiers but are still loaded as classes from the class path.
deprecated
removed
fixed
- Do not crash if more than one artifact reference points to the same file (#25, #29, #35)
- Fix Java 9+ module-version problems with multi-release jars (#31, #33)
- Triage and fix outdated bugs (#23, #20, #17)
security
Version 1.3.0
Version 1.2.1
Release 1.2.0
Starting with this release, the duplicate-finder plugin requires Java 7! If you are still stuck with Java 6, use the 1.1.x versions of this plugin.
- Add includePomProjects configuration setting to allow projects with POM packaging to be checked. Suggested by #11. Thanks @camshoff.
- Allow inclusion of multiple artifacts that may map to the same local project. This fixes issue #10 (thanks @jakub-bochenski).
Release 1.1.2
Fix a bug where an exception is ignored if more conflicts are listed in the exception than actually conflicting jars are present.
Release 1.1.1
- Issue #9. Ignore project references that are not on the dependency list. Thanks @victornoel.
- Add maven properties for all simple (boolean, int, string) configuration settings.
- Ning Issue #44: Allow duplicate checking against elements from the boot classpath
(this includes rt.jar). - Ning Issue #19: Report a defined message if plugin skips execution.