Skip to content

Releases: apache/logging-parent

10.1.0

28 Sep 10:54
@vy vy
rel/10.1.0
5484f2d
Compare
Choose a tag to compare

This minor release focuses on shipping AsciiDoc-based website generation convenience targeting the src/site folder. As a part of this effort, logging-parent started publishing its own website and log4j-changelog support is switched from Markdown to AsciiDoc.

The introduced bnd-maven-plugin default auto-generates both OSGi and JPMS descriptors. Users only need to annotate packages that are to be exported with org.osgi.annotation.bundle.Export, plugin will do the rest of the magic. Hence, no need for custom .bnd and/or module-info.java files anymore. In particular, we expect the absence of module-info.java files to avoid several IDE and testing related headaches.

Added

  • Added asciidoc and constants-tmpl-adoc profiles to generate AsciiDoc-based websites from src/site
  • Added support to auto-generate changelog entries for dependabot updates
  • Added bnd-maven-plugin defaults to auto-generate both OSGi and JPMS descriptors
  • Added CI report uploading in case of test or reproducibility failures (#28)
  • Started publishing the project website

Changed

  • Switched the default log4j-changelog configuration from Markdown (.release-notes.md.ftl and .index.md.ftl) to AsciiDoc (.release-notes.adoc.ftl and .index.adoc.ftl)
  • Update actions/checkout to version 4.1.0
  • Update com.github.spotbugs:spotbugs-maven-plugin to version 4.7.3.6
  • Update com.google.errorprone:error_prone_core to version 2.22.0
  • Update org.apache:apache to version 30
  • Update org.osgi:osgi.annotation to version 8.1.0

Removed

  • Removed project.build.outputTimestamp override since it is already provided by the parent POM and its old value 0 was causing reproducibility issues for spring-boot:repackage

Fixed

  • Replaced incorrect java.version Maven property override with maven.compiler.{source,release,target}

10.0.0

12 Sep 13:35
@vy vy
rel/10.0.0
2af643f
Compare
Choose a tag to compare

This minor release contains various improvements that we expect to relieve the load on pom.xml and GitHub Actions workflows of Maven-based projects we parent. This is of particular importance while managing and cutting releases from multiple repositories. See README.adoc for the complete list of features and their usage.

See this log4j-tools GitHub Actions workflow run demonstrating a successful release cut using a SNAPSHOT version of this logging-parent release. All preparations (release notes, source and binary distributions, vote & announcement emails, etc.) are staged to both Nexus and SVN and waiting the release manager to proceed.

Changes

Added

  • Added changelog-export profile to easily export changelogs to Markdown files
  • Added changelog-release profile to easily move src/changelog/.?.x.x contents to their associated release directory
  • Added deploy profile to ease the Maven deploy goal
  • Added distribution profile to easily create a distribution file containing Git-tracked sources, release notes, binary attachments, NOTICE.txt, etc.
  • Documented release instructions (i.e., RELEASING.md)
  • Added release profile to share common release-specific Maven configuration
  • Added reusable GitHub Actions workflows to share CI boilerplate for other repositories
  • Switched to using log4j-changelog-maven-plugin for managing changelog and release notes

Changed

  • Switched to semantic versioning (old version: 9, new version: 10.0.0)