Hi Andreas,
DependencyResolver is indeed the correct class to use.
Any of the overloaded methods will do: When you have the dependecy, you
can use it directly.
In other cases use DependableCoordinate, which represents an instance that
can contain dependencies.
That can either be a MavenProject, Dependency or Plugin.
To control the scope you need to specify a filter, in your case the
ScopeFilter[1]
This should be the information you were looking for,
Robert
[1]
https://maven.apache.org/shared/maven-common-artifact-filters/apidocs/org/apache/maven/shared/artifact/filter/resolve/ScopeFilter.html
On Mon, 20 Nov 2017 17:08:19 +0100, Andreas Sewe
<s...@st.informatik.tu-darmstadt.de> wrote:
Hi,
I am currently struggling with the maven-artifact-transfer 0.9.1 API.
Here's what I am trying to accomplish: Given an arbitrary GAV and a
scope (compile or test), construct the compile- or test-scoped flat
classpath for that GAV.
DependencyResolver seems to be the class I am after, but I haven't found
out whether to use the Dependency-based or DependableCoordinate-based
overload of resolveDependencies (the Model-based overload won't work, as
I have just a GAV and no Model for it). Also, I haven't figured out how
to specify the scope I am after (dependency:build-classpath doesn't use
maven-artifact-transfer but rather get its information out of the
current project's Model).
And pointers are greatly appreciated.
Best wishes,
Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
