[
https://issues.apache.org/jira/browse/MDEP-568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16596188#comment-16596188
]
Lasse Westh-Nielsen commented on MDEP-568:
------------------------------------------
Big +1 to getting this merged!
I have the same problem as [~cstejerean], caching 3rd party dependencies in CI/
avoiding downloading dependencies when build agent comes up from AWS AMI.
In fact I'm looking at these 3 and getting the same problem: can't grab
dependencies without compiling:
* dependency:copy-dependencies
Goal that copies the project dependencies from the repository to a defined
location
* dependency:go-offline
Goal that resolves all project dependencies, including plugins and reports and
their dependencies
* dependency:resolve
Goal that resolves the project dependencies from the repository. When using
this goal while running on Java 9 the module names will be visible as well
So which one is right for my use case? The difference is too subtle. Deffo
go-offline?
> dependency:go-offline -DexcludeGroupIds=xxxx still try to resolve artifacts
> in the excluded group xxxx
> ------------------------------------------------------------------------------------------------------
>
> Key: MDEP-568
> URL: https://issues.apache.org/jira/browse/MDEP-568
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: go-offline, resolve
> Affects Versions: 2.3, 3.0.0
> Environment: windows / cygwin xp64 bit / bash / maven 3.0.3
> Reporter: Archimedes Trajano
> Priority: Major
> Attachments: MDEP-568-maven-dependency-plugin.patch,
> go-offline_copy-dependencies_patch_sample.zip, test.tgz
>
>
> see thread:
> http://mail-archives.apache.org/mod_mbox/maven-users/201109.mbox/%3c0B02C46601D44673A4A2DF4C4F907E9E@black%3e
> in attached sample pom structure:
> mvn org.apache.maven.plugins:maven-dependency-plugin:2.3:go-offline
> -DexcludeGroupIds=us.pdinc.foo.maven.test
> fails
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)