Return-Path: 
 <users-return-132413-apmail-maven-users-archive=maven.apache.org@maven.apache.org>
X-Original-To: apmail-maven-users-archive@www.apache.org
Delivered-To: apmail-maven-users-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 699D3D310
	for <apmail-maven-users-archive@www.apache.org>;
 Tue, 14 May 2013 08:48:39 +0000 (UTC)
Received: (qmail 20670 invoked by uid 500); 14 May 2013 08:48:37 -0000
Delivered-To: apmail-maven-users-archive@maven.apache.org
Received: (qmail 20507 invoked by uid 500); 14 May 2013 08:48:37 -0000
Mailing-List: contact users-help@maven.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:users-unsubscribe@maven.apache.org>
List-Help: <mailto:users-help@maven.apache.org>
List-Post: <mailto:users@maven.apache.org>
List-Id: "Maven Users List" <users.maven.apache.org>
Reply-To: "Maven Users List" <users@maven.apache.org>
Delivered-To: mailing list users@maven.apache.org
Received: (qmail 20493 invoked by uid 99); 14 May 2013 08:48:36 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 14 May 2013 08:48:36 +0000
X-ASF-Spam-Status: No, hits=1.5 required=5.0
	tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of
 stephen.alan.connolly@gmail.com designates 209.85.212.171 as permitted
 sender)
Received: from [209.85.212.171] (HELO mail-wi0-f171.google.com)
 (209.85.212.171)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 14 May 2013 08:48:32 +0000
Received: by mail-wi0-f171.google.com with SMTP id hq7so2009339wib.16
        for <users@maven.apache.org>; Tue, 14 May 2013 01:48:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:x-received:in-reply-to:references:date:message-id
         :subject:from:to:content-type;
        bh=Et8i9vbTSK9tYwkCda9dSmN4C8nuenTWlkoPjfZlfpo=;
        b=MYheXDBM1SQoZJ5L+BvrJjmIstefeHGUsRBEixT/j0H2ww9Vce2eKNKyZcGerDd2Ma
         MIrB1VtT0YnfO1S3NTisQ1pajMM0SGSEdB+86WjqbT8qJ9C5PXA/9QBr5W7q4imjCzTT
         qBiWO8oKOnC2pAKlN+QMBzHqg+8eP6qUfUdkbqsgDfWA7ZQCLp5QkJKMgiS4ZHeEOkXn
         QK4xbdYfwA3FTq0OT/WrYhKaXleajELhvs5oEsYviL5G9xRuPIGJBLBt1LXW4zOcw3+t
         2BUm/NrKpH3HDwvBcEL3/KxCnPn/4UZSfJV+XRMOTSRGVD+3anuCMGBHBl6EkVUSLt5v
         ccfg==
MIME-Version: 1.0
X-Received: by 10.180.210.242 with SMTP id mx18mr4254810wic.14.1368521291322;
 Tue, 14 May 2013 01:48:11 -0700 (PDT)
Received: by 10.194.37.198 with HTTP; Tue, 14 May 2013 01:48:11 -0700 (PDT)
In-Reply-To: <5191F85B.8090002@ast.dfs.de>
References: <5191F151.9020601@ast.dfs.de>
	<CA+nPnMy8AD+ucsSFV76d530xTtw3V5GkZ8AQ5OcTmAziYWhGGg@mail.gmail.com>
	<5191F85B.8090002@ast.dfs.de>
Date: Tue, 14 May 2013 09:48:11 +0100
Message-ID: 
 <CA+nPnMyOxWK-jy9E85bCVPy7=GhFFjJqLhpbY9pW6rC8HC+NLQ@mail.gmail.com>
Subject: Re: Mismatch by inherited dependencies
From: Stephen Connolly <stephen.alan.connolly@gmail.com>
To: Maven Users List <users@maven.apache.org>
Content-Type: multipart/alternative; boundary=001a11c262e86fdbb104dca9b114
X-Virus-Checked: Checked by ClamAV on apache.org

--001a11c262e86fdbb104dca9b114
Content-Type: text/plain; charset=ISO-8859-1

Well without seeing your parent tree's xpath:/project/dependencies and your
project's xpath:/project/dependencies we cannot say anything as what you
have provided there should *never* end up on the transitive dependency
tree, so you are looking at the wrong part of the pom.


On 14 May 2013 09:39, Sven Bauhan <sven.bauhan@ast.dfs.de> wrote:

> Ok, perhaps you can tell me what I did wrong.
> I included the javadoc plugin by:
>             <plugin>
> <groupId>org.apache.maven.**plugins</groupId>
> <artifactId>maven-javadoc-**plugin</artifactId>
>                 <version>2.9</version>
>                 <configuration>
>                     <author>false</author>
>                     <linksource>true</linksource>
> <docfilessubdirs>true</**docfilessubdirs>
>                     <sourceFileExcludes>
> <exclude>*Adapter*.java</**exclude>
> <exclude>*ObjectFactory.java</**exclude>
> <exclude>*ContextComponent.**java</exclude>
> <exclude>*Configuration.java</**exclude>
> <exclude>*SendController.java<**/exclude>
>                     </sourceFileExcludes>
> <sourcepath>${basedir}/src/**main/java/de/dfs/msg/atsm;${**
> basedir}/target/generated-**sources/xjc/de/dfs/msg/atsm</**sourcepath>
>                 </configuration>
>                 <executions>
>                     <execution>
>                         <id>attach-javadocs</id>
>                         <goals>
>                             <goal>jar</goal>
>                         </goals>
>                     </execution>
>                 </executions>
>             </plugin>
>
> I did not define an explicit dependency to javadoc, but in "mvn
> dependency:tree" I can see it.
>
> Thanks, Sven
>
>
> On 05/14/13 10:18, Stephen Connolly wrote:
>
>> I think you are doing it wrong if you are adding <dependency> for plugins.
>> The xpath:/project/dependencies are about specifying the classpath
>> dependencies during different scopes. The
>> xpath:/project/build/plugins/**plugin entries are about specifying what
>> build
>> tools to use when building the artifact... such build tools are not passed
>> to dependent projects.
>>
>> I am 99.99999999999% certain that you have made a mistake adding
>> maven-javadoc-plugin as a dependency
>>
>>
>> On 14 May 2013 09:09, Sven Bauhan <sven.bauhan@ast.dfs.de> wrote:
>>
>>  Hi, I have another question:
>>>
>>> I have two projects, one java library and a swing application using this
>>> library. For the library I use the apache maven-javadoc-plugin to create
>>> an
>>> API documentation, cause this library shall be used by various
>>> applications.
>>>
>>> The swing application has a dependency to this library and so it also
>>> gets
>>> an inherited dependency to the javadoc plugin. With this also log4j is
>>> inherited as dependency, but with an old version.
>>> In the application also log4j is used, but the latest version. So we have
>>> a version conflict.
>>>
>>> We could solve this yet by excluding the javadoc plugin in the dependency
>>> description:
>>>      <dependency>
>>>        <groupId>de.dfs.msg.atsm</****groupId>
>>>        <artifactId>atsm-camel</****artifactId>
>>>        <version>0.1-SNAPSHOT</****version>
>>>        <exclusions>
>>>          <exclusion>
>>>            <artifactId>maven-javadoc-****plugin</artifactId>
>>>            <groupId>org.apache.maven.****plugins</groupId>
>>>
>>>          </exclusion>
>>>        </exclusions>
>>>      </dependency>
>>> But this is not a good way to do, cause this has to be done by all
>>> applications using the library.
>>>
>>> Is there a way to define the dependency in the library pom not to be
>>> inherited?
>>> I saw there is a scope definition for dependencies, but I did not
>>> understand this concept yet. Would this be a solution?
>>>
>>> Thanks,
>>> Sven
>>>
>>>
>>> ------------------------------****----------------------------**
>>> --**---------
>>> To unsubscribe, e-mail: users-unsubscribe@maven.**apac**he.org<http://apache.org>
>>> <users-unsubscribe@**maven.apache.org<users-unsubscribe@maven.apache.org>
>>> >
>>>
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>>
>>>
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: users-unsubscribe@maven.**apache.org<users-unsubscribe@maven.apache.org>
> For additional commands, e-mail: users-help@maven.apache.org
>
>

--001a11c262e86fdbb104dca9b114--