Return-Path: 
 <dev-return-88452-apmail-ant-dev-archive=ant.apache.org@ant.apache.org>
X-Original-To: apmail-ant-dev-archive@www.apache.org
Delivered-To: apmail-ant-dev-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 821A617BC0
	for <apmail-ant-dev-archive@www.apache.org>;
 Thu,  9 Apr 2015 08:59:24 +0000 (UTC)
Received: (qmail 77322 invoked by uid 500); 9 Apr 2015 08:59:15 -0000
Delivered-To: apmail-ant-dev-archive@ant.apache.org
Received: (qmail 77259 invoked by uid 500); 9 Apr 2015 08:59:14 -0000
Mailing-List: contact dev-help@ant.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:dev-unsubscribe@ant.apache.org>
List-Help: <mailto:dev-help@ant.apache.org>
List-Post: <mailto:dev@ant.apache.org>
List-Id: "Ant Developers List" <dev.ant.apache.org>
Reply-To: "Ant Developers List" <dev@ant.apache.org>
Delivered-To: mailing list dev@ant.apache.org
Received: (qmail 77245 invoked by uid 99); 9 Apr 2015 08:59:14 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 Apr 2015 08:59:14 +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 (nike.apache.org: domain of g.grigelionis@gmail.com
 designates 209.85.214.171 as permitted sender)
Received: from [209.85.214.171] (HELO mail-ob0-f171.google.com)
 (209.85.214.171)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 Apr 2015 08:58:22 +0000
Received: by obbfy7 with SMTP id fy7so5745381obb.2
        for <dev@ant.apache.org>; Thu, 09 Apr 2015 01:58:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:date:message-id:subject:from:to:content-type;
        bh=+i4cCJVRV1GkM7Z0PGNvjK4qiJ5N0K3GQxImrQTptf8=;
        b=EGAXQNlhnxo9Ct/T0vELoF2NN3/e7DWwibSW7MGi7tIiKdeXEivD+9H9FKusCO4wiw
         OCC1MdLnx8bxHhfWFR2CxghDalg2Ym/2TRbLy64ayfUpDYR2KRPQESi0/3lnSAkcwYYO
         vdF+iwVFO3RFczIGRij4ruBb86NOX7VatFJmM7jHhYT3urlGc3yQwtzmes60hd9TP6Hi
         Nmj7HYuXcsX7GRUypAVMv7zwQ2ZYGmGoG2e6GChrQXtTRF3koI1QI+eq5yOmccpQQ6wk
         rYhCPF+oIbXQWDaV1tk9MnSWlyZw97nwcqOC5jPMtWHenEjXVuUaPXY4gVcLai87oRdp
         AUCg==
MIME-Version: 1.0
X-Received: by 10.60.85.98 with SMTP id g2mr36985071oez.74.1428569900088; Thu,
 09 Apr 2015 01:58:20 -0700 (PDT)
Received: by 10.182.197.10 with HTTP; Thu, 9 Apr 2015 01:58:20 -0700 (PDT)
Date: Thu, 9 Apr 2015 10:58:20 +0200
Message-ID: 
 <CALVNWHUh1WS0Hej5oH+Wg0C85aE71BgUGynqG_UaFJtK-K4mEg@mail.gmail.com>
Subject: Ivy "extends" loses defaultconfmapping
From: Gintautas Grigelionis <g.grigelionis@gmail.com>
To: Ant Developers List <dev@ant.apache.org>
Content-Type: multipart/alternative; boundary=089e0111bc2c6e83cb051346d94d
X-Virus-Checked: Checked by ClamAV on apache.org

--089e0111bc2c6e83cb051346d94d
Content-Type: text/plain; charset=UTF-8

I tried to use extends tag to avoid boilerplate configurations like this

<ivy-module ...>
  <info organisation="a" module="b">
     <extends organisation="c" module="d" revision="1"
extendType="configurations"/>
  </info>

  <publications>
   ...
  </publications>

  <dependencies>
   ...
  </dependencies>
</ivy-module>

The ivy.xml containing configurations is

<ivy-module ...>
    <info organisation="c" module="d" revision="1" status="integration"
publication="..."/>
    <configurations defaultconfmapping="*->@">
        <conf name="provided" transitive="true" description="Required for
compilation, but provided by the container or JRE at runtime."/>
        <conf name="compile" transitive="true" description="Required for
compilation"/>
        <conf name="runtime" transitive="true" extends="compile" description
="Required at runtime"/>
        <conf name="test" transitive="true" extends="runtime"
description="Required
for test only"/>
    </configurations>
    <publications>
        <artifact name="d" type="pom" ext="pom" conf="compile"/>
    </publications>
</ivy-module>

I generate corresponding pom and publish it with ivy.xml so that I can run
publish as usual and have something to resolve for.

The resulting ivy.xml that is published looks like this

<ivy-module ...>
    <info organisation="a" module="b" revision="..." status="integration"
publication="...">
        <!-- <extends organisation="c" module="d" revision="1"
extendType="configurations"/> -->
    </info>

    <configurations>
        <!-- configurations inherited from c#d;1 -->
        <conf name="provided" visibility="public" description="Required to
compile application, but provided by the container or JRE at runtime."/>
        <conf name="compile" visibility="public" description="Required to
compile application"/>
        <conf name="runtime" visibility="public" description="Required at
runtime" extends="compile"/>
        <conf name="test" visibility="public" description="Required for
test only" extends="runtime"/>
    </configurations>

    <publications>
...     </publications>

    <dependencies>        ...
    </dependencies>
</ivy-module>
Please note the missing defaultconfmapping, which lets Ivy to revert to
default defaultconfmapping ("*->*") which has the effect of putting all
configurations together with all other configurations, making
configurations useless in resolve.
Is this a bug or am I missing something?

I noticed other effects of "extends" that are undocumented, like looking
for a "parent" ivy.xml on resolve in ".." (undocumented default value for
location attribute + location having preference over resolvers even when
not specified explicitly?) and treating the repository name where the
resolved ivy.xml used for extending was found as a resolver reference name
on retrieve and complaining that that name was not defined in Ivy settings.

--089e0111bc2c6e83cb051346d94d--