Return-Path: 
 <users-return-133694-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 8156F1033D
	for <apmail-maven-users-archive@www.apache.org>;
 Fri, 30 Aug 2013 15:48:31 +0000 (UTC)
Received: (qmail 97178 invoked by uid 500); 30 Aug 2013 15:48:28 -0000
Delivered-To: apmail-maven-users-archive@maven.apache.org
Received: (qmail 97000 invoked by uid 500); 30 Aug 2013 15:48:23 -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 96988 invoked by uid 99); 30 Aug 2013 15:48:22 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 30 Aug 2013 15:48:22 +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: local policy)
Received: from [91.221.255.2] (HELO messenger-ptx.axway.net) (91.221.255.2)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 30 Aug 2013 15:48:17 +0000
X-WSS-ID: 0MSCP2K-21-2LS-02
X-M-MSG: 
Received: from WPTXCAS2.ptx.axway.int (unknown [10.128.17.52])
	(using TLSv1 with cipher AES128-SHA (128/128 bits))
	(No client certificate requested)
	by messenger-ptx.axway.net (Postfix) with ESMTPS id 250D46B961F
	for <users@maven.apache.org>; Fri, 30 Aug 2013 17:44:44 +0200 (CEST)
Received: from WPTXMAIL1.ptx.axway.int ([::1]) by WPTXCAS2.ptx.axway.int
 ([::1]) with mapi id 14.03.0146.000; Fri, 30 Aug 2013 17:47:39 +0200
From: David Gay <dgay@axway.com>
To: "users@maven.apache.org" <users@maven.apache.org>
Subject: Maven Shade-Plugin strange behavior
Thread-Topic: Maven Shade-Plugin strange behavior
Thread-Index: Ac6lmEEnI0nZL/1LT4iZorxbr3va5w==
Date: Fri, 30 Aug 2013 15:47:39 +0000
Message-ID: <1506FFE6E7E2FA4A9381BFB87F99B48199DDCAA5@WPTXMAIL1.ptx.axway.int>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.131.10.202]
Content-Type: multipart/alternative;
	boundary="_000_1506FFE6E7E2FA4A9381BFB87F99B48199DDCAA5WPTXMAIL1ptxaxw_"
MIME-Version: 1.0
X-Virus-Checked: Checked by ClamAV on apache.org

--_000_1506FFE6E7E2FA4A9381BFB87F99B48199DDCAA5WPTXMAIL1ptxaxw_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi all,

I would like to know if this behavior is normal while using the maven-shade=
-plugin.

Take this sample pom as input:
<project>
                <modelVersion>4.0.0</modelVersion>
                <groupId>sample</groupId>
                <artifactId>shade-effect</artifactId>
                <packaging>jar</packaging>
                <version>1.0.0-SNAPSHOT</version>
                <build>
                               <plugins>
                                               <plugin>
                                                               <groupId>org=
.apache.maven.plugins</groupId>
                                                               <artifactId>=
maven-shade-plugin</artifactId>
                                                               <version>2.1=
</version>
                                                               <executions>
                                                                           =
   <execution>
                                                                           =
                   <phase>package</phase>
                                                                           =
                   <goals>
                                                                           =
                                   <goal>shade</goal>
                                                                           =
                   </goals>
                                                                           =
                   <configuration>
                                                                           =
                                   <createDependencyReducedPom>true</create=
DependencyReducedPom>
                                                                           =
                   </configuration>
                                                                           =
   </execution>
                                                               </executions=
>
                                               </plugin>

                               </plugins>
                </build>
                <dependencies>
                               <dependency>
                                               <groupId>commons-io</groupId=
>
                                               <artifactId>commons-io</arti=
factId>
                                               <version>2.4</version>
                               </dependency>
                               <dependency>
                                               <groupId>org.mockito</groupI=
d>
                                               <artifactId>mockito-core</ar=
tifactId>
                                               <version>1.9.5</version>
                                               <scope>test</scope>
                               </dependency>
                </dependencies>
</project>

And do a mvn clean install.
The real pom that is deployed in the repository is the one that has been "t=
ransformed" by the shade plugin (ie: dependency-reduced-pom.xml)
If I look at this pom, the compile dependencies are removed as expected. Go=
od.
But, if you look at the dependencies with scope test, they is a super stran=
ge behavior:

<project>
  <modelVersion>4.0.0</modelVersion>
  <groupId>sample</groupId>
  <artifactId>shade-effect</artifactId>
  <version>1.0.0-SNAPSHOT</version>
  <build>
    <plugins>
      <plugin>
        <artifactId>maven-shade-plugin</artifactId>
        <version>2.1</version>
        <executions>
          <execution>
            <phase>package</phase>
            <goals>
              <goal>shade</goal>
            </goals>
            <configuration>
              <createDependencyReducedPom>true</createDependencyReducedPom>
            </configuration>
          </execution>
        </executions>
      </plugin>
    </plugins>
  </build>
  <dependencies>
    <dependency>
      <groupId>org.mockito</groupId>
      <artifactId>mockito-core</artifactId>
      <version>1.9.5</version>
      <scope>test</scope>
      <exclusions>
        <exclusion>
          <artifactId>hamcrest-core</artifactId>
          <groupId>org.hamcrest</groupId>
        </exclusion>
        <exclusion>
          <artifactId>objenesis</artifactId>
          <groupId>org.objenesis</groupId>
        </exclusion>
      </exclusions>
    </dependency>
  </dependencies>
</project>

Why are all the transitive dependencies of the test artifacts being exclude=
d ????
It surprise me a lot (and made some of my jobs fails in specific situations=
, for example when using Sonar, but that's another story/problem)

BTW: I use Maven 3.0.5

Thanks for your help.
WBR // David


--_000_1506FFE6E7E2FA4A9381BFB87F99B48199DDCAA5WPTXMAIL1ptxaxw_--