You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Dimitri R (JIRA)" <ji...@apache.org> on 2018/06/13 03:26:00 UTC
[jira] [Updated] (MDEP-620) mvn dependency:unpack via CLI generates
${project.basedir} folder
[ https://issues.apache.org/jira/browse/MDEP-620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dimitri R updated MDEP-620:
---------------------------
Environment:
* Maven 3.5.3
* CLI
* macOS and CentOS
was:
* Maven 3.5.3
* CLI
* macOS and Debian
> mvn dependency:unpack via CLI generates ${project.basedir} folder
> -----------------------------------------------------------------
>
> Key: MDEP-620
> URL: https://issues.apache.org/jira/browse/MDEP-620
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: unpack
> Environment: * Maven 3.5.3
> * CLI
> * macOS and CentOS
> Reporter: Dimitri R
> Priority: Major
>
> h3. Steps to reproduce
> 1. Get a sample dependency first
> {noformat}
> mvn dependency:get -DgroupId=org.apache.ant -DartifactId=ant -Dversion=1.8.3 -Dpackaging=jar
> {noformat}
> 2. Delete the file *~/.m2/repository/org/apache/ant/ant/1.8.3/_remote.repositories*
> 3. Unpack the dependency somewhere
> {noformat}
> cd /tmp
> mkdir unpack
> mvn dependency:unpack -Dartifact=org.apache.ant:ant:1.8.3:jar -DoutputDirectory=./unpack
> {noformat}
> 4. Observe that *${project.basedir}* was created
> {noformat}
> $ ls -l /tmp/unpack
> total 0
> ... ${project.basedir}
> ... unpack
> {noformat}
> *_Note_* Step 2 is only necessary because of _getting_ the dependency, this wouldn't have to be done if it had been _installed_. This doesn't affect whether the bug occurs or not.
> ----
> Similar/related issues (their fixes don't apply here):
> - [https://stackoverflow.com/q/11669446/321797]
> - [https://netbeans.org/bugzilla/show_bug.cgi?id=221560]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)