You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Tamas Cservenak (Jira)" <ji...@apache.org> on 2024/09/22 09:17:00 UTC

[jira] [Assigned] (MNG-8263) Remove last remnants of wrapper integration into core

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

Tamas Cservenak reassigned MNG-8263:
------------------------------------

    Assignee: Tamas Cservenak

> Remove last remnants of wrapper integration into core
> -----------------------------------------------------
>
>                 Key: MNG-8263
>                 URL: https://issues.apache.org/jira/browse/MNG-8263
>             Project: Maven
>          Issue Type: Task
>          Components: Bootstrap &amp; Build, Core
>            Reporter: Tamas Cservenak
>            Assignee: Tamas Cservenak
>            Priority: Major
>             Fix For: 4.0.0, 4.0.0-beta-5
>
>
> At early beginning of ingesting Takari Wrapper, several ideas were tried until wrapper arrived to it's final place.
> Still, there are some remnants in master that complicates our lives and also results in strange side effects:
> * lifecycle - this makes Maven4 be fixed regarding used Wrapper (unless explicitly set in POM, but wrapper is not a lifecycle plugin, so should not be set in POM)
> * mvn/mvn.cmd scripts - they were split to make them reusable for wrapper, but today there is no need for this. Still, split scripts are hard to manage/edit/validate with tools.



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