You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Konrad Windszus (Jira)" <ji...@apache.org> on 2022/12/16 07:51:00 UTC

[jira] [Closed] (JCRVLT-642) Drop Plexus components and only rely on JSR 330

     [ https://issues.apache.org/jira/browse/JCRVLT-642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Konrad Windszus closed JCRVLT-642.
----------------------------------

> Drop Plexus components and only rely on JSR 330
> -----------------------------------------------
>
>                 Key: JCRVLT-642
>                 URL: https://issues.apache.org/jira/browse/JCRVLT-642
>             Project: Jackrabbit FileVault
>          Issue Type: Improvement
>          Components: package maven plugin
>    Affects Versions: package-maven-plugin-1.3.0
>            Reporter: Konrad Windszus
>            Assignee: Konrad Windszus
>            Priority: Major
>             Fix For: package-maven-plugin-1.3.2
>
>
> 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.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)