You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "林万程 (Jira)" <ji...@apache.org> on 2020/12/02 06:49:00 UTC
[jira] [Created] (MDEP-731) Picking out dependencies to a new
repository
林万程 created MDEP-731:
------------------------
Summary: Picking out dependencies to a new repository
Key: MDEP-731
URL: https://issues.apache.org/jira/browse/MDEP-731
Project: Maven Dependency Plugin
Issue Type: New Feature
Affects Versions: 3.1.2
Reporter: 林万程
Many companies will have their own company's private jars. When copying, they often need to copy the entire warehouse, but in fact not all files are needed. I hope to have the function of picking out dependencies to a new warehouse (including all files in the corresponding directory, Such as jar, javadoc.jar, metadata, but not *.lastUpdated, _remote.repositories.
The command can be:
{code:java}
mvn dependency:pick -DnewRepo=D:/.m2/myRepo{code}
Sometimes only the jars that are not available in the remote warehouse are needed. I hope to automatically check if there are any in the remote warehouse and pick out the jars that are not available.
The command can be:
{code:java}
mvn dependency:pick -DnewRepo=D:/.m2/myRepo -DonlyLocal=true{code}
{code:java}
mvn dependency:pick -DnewRepo=D:/.m2/myRepo -DonlyLocal=true -Durl=https://repo.maven.apache.org/maven2/{code}
{code:java}
mvn dependency:pick -DnewRepo=http://myNexus/repository/myRepo/ -DonlyLocal=true -Durl=https://repo.maven.apache.org/maven2/{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)