Open kwin opened 3 years ago
An algorithm like https://github.com/bndtools/bnd/blob/885ee4045ab3ffe4205473063c8f7f8b42c9abfa/maven/bnd-baseline-maven-plugin/src/main/java/aQute/bnd/maven/baseline/plugin/BaselineMojo.java#L210 is necessary to determine the base version correctly.
Probably injecting the version with https://www.mojohaus.org/versions-maven-plugin/update-property-mojo.html is the easiest approach.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
The test in
com.adobe.acs.commons.it.build.ScrMetadataIT
always compares with metadata from the latest ACS Commons release. Instead it should compare with the latest release version which is smaller than the current snapshot. We currently have build failures in https://github.com/Adobe-Consulting-Services/acs-aem-commons/tree/feature/2288-prepare-release-500 due to that (as that is still based on 4.8.6-SNAPSHOT). Only that way parallel evolution of two major releases is properly supported.