You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by "Gintas Grigelionis (JIRA)" <ji...@apache.org> on 2018/02/02 20:11:00 UTC

[jira] [Commented] (IVY-1459) include in dependency doesn't work as expected with extra attributes

    [ https://issues.apache.org/jira/browse/IVY-1459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16350893#comment-16350893 ] 

Gintas Grigelionis commented on IVY-1459:
-----------------------------------------

Hi Olivier, could you please try a [build from master|https://teamcity.jetbrains.com/viewLog.html?&buildTypeId=bt125&buildId=lastSuccessful] (sorry, Apache Jenkins builds sometimes fail for reasons not related to coding issues)? The attributes on include were silently ignored before.

> include in dependency doesn't work as expected with extra attributes
> --------------------------------------------------------------------
>
>                 Key: IVY-1459
>                 URL: https://issues.apache.org/jira/browse/IVY-1459
>             Project: Ivy
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.3.0
>         Environment: GNU/Linux, Ivy 2.3.0, Ant 1.9.2, Java 6 SUN
>            Reporter: Olivier Patry
>            Priority: Major
>              Labels: dependency, include
>
> Hi,
> I try to combine <include /> tag in dependency and extra attributes which seems not allowed according to the documentation (since it is not mentioned that <include /> allows extra attributes).
> Why not allowed?
> Can it be allowed?
> Moreover, the actual behavior seems buggy since several artifacts can be resolved with the same regexp but only one is used and no error occurs.
> I currently use <conf name="" mapped=""/> in combination with the <include /> tag, so that I can resolve artifacts from regexp restricted to a given set of configurations. If I keep only conf mapping, let's say I get 36 artifacts, then if I had a <include name="*" />, I get only 12 of them (should be the same result since the include rule doesn't expose any restriction). This is related to the first issue where no error occurs for several artifacts matches.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)