Uploaded image for project: 'Maven'
  1. Maven
  2. MNG-7260 Remove old deprecated code
  3. MNG-7266

Remove maven-compat module

Attach filesAttach ScreenshotAdd voteVotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Open
    • Major
    • Resolution: Unresolved
    • None
    • 4.x / Backlog
    • None
    • None

    Description

      Maven-core does not depend on maven-compat anymore (runtime or compile time). Do we want to carry it over up to 4.0.0 and delete it in 4.1.0, or do we want to drop it before 4.0.0 ?

      Tamas Cservenak Olivier Lamy Romain Manni-Bucau Slawomir Jaranowski and others... ?

      Attachments

        Issue Links

        depends upon

        Improvement - An improvement or enhancement to an existing feature or task. MRRESOURCES-118 Require Maven 3.2.5

        • Major - Major loss of function.
        • Closed
        is blocked by

        Improvement - An improvement or enhancement to an existing feature or task. MNG-7809 Make maven-compat optional

        • Major - Major loss of function.
        • Closed
        is part of

        Task - A task that needs to be done. MNG-7260 Remove old deprecated code

        • Major - Major loss of function.
        • Open
        relates to

        Task - A task that needs to be done. MPLUGIN-377 Drop use of legacy APIs

        • Major - Major loss of function.
        • Closed
        links to

        Web Link GitHub Pull Request #1487

        Activity
          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned
            gnodet Guillaume Nodet
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:

              Slack

                Issue deployment