I think that is a bug that is in scope for 3.5.1 or 3.6.0
On 31 May 2017 at 22:30, Laird Nelson wrote:
> (I've been working with Maven since at least 2004 and I think I *still*
> don't
> get transitive dependencies.)
>
> I have a pom.xml file of type pom that has some compile-scoped dependencies
(I've been working with Maven since at least 2004 and I think I *still* don't
get transitive dependencies.)
I have a pom.xml file of type pom that has some compile-scoped dependencies
in it. (P1 -> A(compile), B(compile))
I have another project that depends on this pom in provided scope (I'm jus
Hi Jamal,
Jamal B wrote:
> Interesting
>
> Taking your suggestion, it looks like it is coming in from another compile
> dependency, and was "promoted" to compile.
>
> [INFO] +- org.apache.maven.shared:maven-shared-jar:jar:1.1:compile
> [INFO] | +- org.codehaus.plexus:plexus-digest:jar:1.0:
Interesting
Taking your suggestion, it looks like it is coming in from another compile
dependency, and was "promoted" to compile.
[INFO] +- org.apache.maven.shared:maven-shared-jar:jar:1.1:compile
[INFO] | +- org.codehaus.plexus:plexus-digest:jar:1.0:compile
[INFO] | | \-
org.codehaus.plex
Hi Jamal,
Jamal B wrote:
> Hello, I have a question about transitive dependencies. According to the
> pom documentation here: http://maven.apache.org/pom.html#Dependencies
>
> project dependencies marked with test scope are not transitive. I assumed
> that this also applied to it's dependencie
Hi, thanks for your response.
Running dependency:list shows also shows that junit is at compile scope
which I expected to be at test scope.
[INFO] --- maven-dependency-plugin:2.7:list (default-cli) @ application ---
[INFO]
[INFO] The following files have been resolved:
[INFO]junit:junit:
Hi,
Tree is showing the tree. So it seems correct at first sight. Its showing
you the dependency beetween your test-utils of the project and junit which
is in fact scope compile.
What you seem to actually want to have is the resolved list of dependencies
for your application project.
That goal is
Hello, I have a question about transitive dependencies. According to the
pom documentation here: http://maven.apache.org/pom.html#Dependencies
project dependencies marked with test scope are not transitive. I assumed
that this also applied to it's dependencies, so my question is if I declare
a d
andard pattern I can find
somewhere or is that an IoC artifact?
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 17, 2005 22:18
To: Maven Users List
Subject: Re: [m2] Transitive Dependency Question
On 8/18/05, Allison, Bob <[EMAIL PROTECTED]> wrote:
On 8/18/05, Allison, Bob <[EMAIL PROTECTED]> wrote:
> What is the correct scope to make this
> work (or do I need to explicitly state the dependency on log4j in the
> logging project)?
Sounds more like a bug in the javadoc plugin. Redeclaring will work as
a workaround, but please file a JIRA issue
On Wed, 2005-08-17 at 19:43 -0500, Allison, Bob wrote:
> I am working on a multi-project which looks like this:
>
> Project log4jext is an extension for log4j for our environment. Because
> of the nature of extending log4j, I was unable to completely remove all
> log4j classes from this project's
I am working on a multi-project which looks like this:
Project log4jext is an extension for log4j for our environment. Because
of the nature of extending log4j, I was unable to completely remove all
log4j classes from this project's API. Its dependencies look like:
log4j
log4j
12 matches
Mail list logo
