[JCRVLT-769] mapPackageDependencyToMavenGa does no longer work

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: package-maven-plugin-1.3.0
• Fix Version/s: package-maven-plugin-1.4.0
• Component/s: package maven plugin
• Assignee: Konrad Windszus
• Reporter: Konrad Windszus
• Created: 09/Aug/24 08:19
• Updated: 01/Oct/24 06:17
• Resolved: 14/Sep/24 08:44

Description

JCRVLT-567 introduced the regression that the manual mapping from package dependency to Maven coordinates was no longer considered (caused by https://github.com/apache/jackrabbit-filevault-package-maven-plugin/commit/829a08abebded00b9c15e4df709b96e28ca2ce08#diff-fb5f20c363b40e1380878e34329d42d8c414e11448aa355a3bd0ecc7b79ad91cL100-L113)

In addition due to https://issues.apache.org/jira/browse/MNG-8192 using the parameter mapPackageDependencyToMavenGa throws exceptions on Maven > 3.6.2 as that does no longer allow Artifacts without a valid version.

Issue Links

• is caused by: MNG-8192 DefaultArtifact constructor no longer accepts empty version
• is caused by: JCRVLT-567 Move ValidationContext implementation to validation module and export them
• is related to: JCRVLT-774 Allow overwriting of AbstractDependencyResolver.resolvePackageInfo(Dependency)