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

Posted to issues@maven.apache.org by "Arne Lewinski (Jira)" <ji...@apache.org> on 2020/02/16 22:29:00 UTC

[jira] [Created] (MNG-6865) copy in object scope rather in class scope

Arne Lewinski created MNG-6865:
----------------------------------

             Summary: copy in object scope rather in class scope
                 Key: MNG-6865
                 URL: https://issues.apache.org/jira/browse/MNG-6865
             Project: Maven
          Issue Type: Improvement
          Components: core
            Reporter: Arne Lewinski


This refactoring refers to a more intuitive API approach.

The interface "MavenExecutionRequest" should provide an object scope method to copy itself. This has to be implemented by each sub type of "MavenExecutionRequest". Neverteless: I only found the class "DefaultMavenExecutionRequest" implementing the interface.
 # Providing an object scope copy method makes the usage less verbose.
 # As the copy method is defined abstract: the MavenCli class got rid of the concrete class "DefaultMavenExecutionRequest" dependency

The static copy method should be declared deprecated and can be made private in the future.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)