[
https://issues.apache.org/jira/browse/MNG-6794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17181146#comment-17181146
]
Martin Kanters commented on MNG-6794:
-------------------------------------
[~michael-o], I just want to verify we understood [~gaurav9822] and the author
of the article correctly (and that I understood your comment correctly).
I interpreted the suggestion of [~gaurav9822] as that you would be able to add
the dependency to the pom.xml file by a mvn cmd (similarly like `npm i
<package> --save` does). In this case it would operate on the project and not
on the local dependency cache. In this case
https://issues.apache.org/jira/browse/MDEP-699 is a duplicate.
If one wants to just download the dependency instead of adding it to the
project's pom.xml, he could use [mvn
dependency:get|https://maven.apache.org/plugins/maven-dependency-plugin/get-mojo.html].
[~gaurav9822], can you give some clarity?
> Add mvn add groupId/artifactId feature like NPM to maven
> --------------------------------------------------------
>
> Key: MNG-6794
> URL: https://issues.apache.org/jira/browse/MNG-6794
> Project: Maven
> Issue Type: Wish
> Reporter: gaurav
> Priority: Minor
>
> The article 10 myths about java in
> 2019(https://developer.okta.com/blog/2019/07/15/java-myths-2019) list a nice
> feature which maven could add to it.
>
> For NPM, Want to add a new dependency? Just run {{npm i groupId/artifactId}}.
>
> do think it would be cool if Maven had something like {{mvn add
> groupId/artifactId}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)