You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Herve Boutemy (Jira)" <ji...@apache.org> on 2023/05/18 15:34:00 UTC
[jira] [Updated] (MDEPLOY-291) Update POM parent and Maven + warn if older Maven is used to build a Maven plugin (as impacted by MNG-7055)
[ https://issues.apache.org/jira/browse/MDEPLOY-291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Herve Boutemy updated MDEPLOY-291:
----------------------------------
Summary: Update POM parent and Maven + warn if older Maven is used to build a Maven plugin (as impacted by MNG-7055) (was: Update POM parent and Maven)
> Update POM parent and Maven + warn if older Maven is used to build a Maven plugin (as impacted by MNG-7055)
> -----------------------------------------------------------------------------------------------------------
>
> Key: MDEPLOY-291
> URL: https://issues.apache.org/jira/browse/MDEPLOY-291
> Project: Maven Deploy Plugin
> Issue Type: Task
> Reporter: Tamas Cservenak
> Assignee: Tamas Cservenak
> Priority: Major
> Fix For: 3.0.0
>
>
> Update plugin build:
> * update parent to 36
> * update maven to 3.8.5 (reasoning below)
> * up the plugin to Java8
> This plugin along with m-install-p versions 3.x line (3.0.0-Mx) _does not work_ with any so far released Maven 3.x line (see MNG-7055). The ONLY maven 3.x they will be usable with is upcoming 3.9.0, that has fix for MNG-7055 backported, but OTOH, it is already Java8, so no point in keeping the plugin on anything below.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)