Skip to content

Latest commit

 

History

History
116 lines (90 loc) · 5 KB

CHANGELOG.md

File metadata and controls

116 lines (90 loc) · 5 KB
Raw

Linkage Checker Enforcer Rule and Linkage Monitor Change Log

1.5.12

  • Fixed the bug in the Gradle plugin that affected artifacts with "pom" packaging (#2196)

1.5.11

  • The Gradle plugin omits duplicate dependency paths when printing the locatin of problematic artifacts (#2188).

1.5.10

  • Fixed the bug that generated false positives on artifacts with classifiers (#2173)
  • Fixed the incorrect handling of protected methods on java.lang.Object (#2177)
  • The Gradle plugin shows partial results even if there are unexpected attributes of dependencies ( #2178).
  • The Gradle plugin checks circular dependencies when showing linkage errors (#2174).
  • The messages about linkage errors include the types of method and field symbols (2179).

1.5.9

  • Added an exclusion rule for invalid references in appengien-api-1.0-sdk (#2045)

1.5.8

  • Fixed the bug of the Linkage Checker enforcer rule not reporting failures when it cannot find exclusion files (#2006)
  • Updated the default exclusion rules with the classes referenced from Netty's optional features (#1977)

1.5.7

  • Fixed the problem of Linkage Monitor recognizing a parent pom as a BOM (#1958). Linkage Monitor now reads linkage-monitor-artifacts.txt for the list of artifacts generated by the repository.

1.5.6

  • Fixed false negative problem in Linkage Monitor where it did not find local artifacts listed in a BOM (#1919).

1.5.5

  • Linkage Monitor is part of the release process.

1.5.4

  • Fixed false positive linkage errors on unused private inner classes (#1608)

1.5.3

  • Linkge Checker can resolve artifacts from different repositories.

1.5.2

  • Linkage Checker enforcer rule works with other repositories than Maven Central.

1.5.1

  • Fixed the NullPointerException bug that occurs when printing certain linkage errors (#1599).

1.5.0

  • Linkage Checker no longer includes optional dependencies when building dependency graphs. This avoids constructing unexpectedly large graphs due to optional dependencies (#1256).
  • Linkage errors now have cause field that can explain the dependency conflicts by analyzing dependency graphs.

1.4.3

  • Made ClassPathEntry.getArtifact() public for the Linkage Checker Gradle plugin

1.4.2

  • Fixed unnecessary graph traversal logic when building dependency graphs

1.4.1

  • Fixed false positive linkage errors in Maven projects with WAR packaging

1.4.0

  • Linkage Checker enforcer rule shows dependency paths to problematic Maven artifacts.
  • Fixed the enforcer rule's incorrect selection of entry point JARs for reachability analysis

1.3.0

  • LinkageCheckerMain has an option (-o) to output linkage errors into a file (document). This feature is currently alpha; we may change the behavior/format in later releases.
  • LinkageCheckerMain throws LinkageCheckResultException if it finds linkage errors.

1.2.1

  • Linkage Checker handles class files containing methods without a body.

1.2.0

  • Linkage Checker takes an exclusion file to filter out linkage errors.
  • Fixed LinkageCheckerMain's incorrect handling of JAR file input

1.1.4

  • Linkage Checker resolves class paths in a more efficient manner.

1.1.3

  • Linkage Checker now reports missing artifacts.
  • Linkage Checker shows dependency paths to Maven artifacts that have linkage errors.

1.1.2

  • Fixed Maven Central URL to use HTTPS

1.1.1

  • The enforcer rule prints unresolved dependencies.

1.1.0

  • The enforcer rule detects unimplemented methods in interfaces and abstract classes.
  • Fixed wrong URL and SCM section in pom.xml

1.0.1

  • The enforcer rule now interpolates the ${os.detect.classifier} property defined by the os-maven-plugin.