[JCRVLT-642] Drop Plexus components and only rely on JSR 330

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: package-maven-plugin-1.3.0
• Fix Version/s: package-maven-plugin-1.3.2
• Component/s: package maven plugin
• Assignee: Konrad Windszus
• Reporter: Konrad Windszus
• Created: 13/Jul/22 06:47
• Updated: 16/Dec/22 07:50
• Resolved: 14/Jul/22 12:29

Description

Currently plexus components are leveraged for the default lifecycle mapping and the artifact handler for type "content-package". Both should be converted to a JSR 330 approach to ensure compatibility with future versions of Maven.

Further information available at https://lists.apache.org/thread/zqz7zvphxst1nb18k32mrxd93vhpzh8y

Also all plugins (except for the filevault one) should have an explicit version in the mapping to make ITs more stable and in general leverage the newest version in cases where the pom.xml doesn't define an explicit version of those without requiring Maven to check the remote repo for the latest version.

Issue Links

• links to: GitHub Pull Request #81