ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tom Eyckmans (JIRA)" <>
Subject [jira] Commented: (IVY-472) conf not supported as pattern filtering token
Date Sun, 02 Nov 2008 21:02:44 GMT


Tom Eyckmans commented on IVY-472:

I'd like to be able to use the [conf] in resolver patterns aswell just because it would simplify
ivy configuration files:

e.g.: I just started trying to build up a local repository from scratch with very controlled
content. First thing I wanted to add was testng-5.8

TestNG has 2 configurations (jdk14 and jdk15). So I set up my local resolver:

                 <url name="my-ivy-rep">
  			<ivy 	  pattern="file:${my.ivy.rep.root}/[organisation]/[module]/ivys/ivy-[revision].xml"/>
  			<artifact pattern="file:${my.ivy.rep.root}/[organisation]/[module]/[type]s/[artifact]-[revision].[ext]"/>
<!-- covers normal artifacts without a [conf] specific name -->
  			<artifact pattern="file:${my.ivy.rep.root}/[organisation]/[module]/[type]s/[artifact]-[revision]-[conf].[ext]"/>
<!-- covers artifacts with a [conf] specific name -->

I made up the TestNG ivy-5.8.xml file containing the 2 configurations and 1 published artifact
for both configurations:

                 <artifact name="testng" type="jar" conf="jdk14,jdk15" ext="jar"/>

Created a project that depended on the jdk15 configuration of TestNG (default->jdk15).

I was very supprised that this did not work. [conf] always resolves to default when it's being
used in the resolver artifact pattern very frustrating. As this would simplify a lot of ivy

As a workaround I'm now renaming the original TestNG jar files (e.g.: testng-5.8-jdk14.jar
-> testng-jdk14-5.8.jar) and add a published artifact for each configuration with a different
base name (testng-jdk14, testng-jdk5).

> conf not supported as pattern filtering token
> ---------------------------------------------
>                 Key: IVY-472
>                 URL:
>             Project: Ivy
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: unspecified
>         Environment: WinXP x86 with Ant1.7
>            Reporter: Todd Lee
>            Priority: Minor
> it seems that [conf] is not currently supported for use as an artifact pattern in an
ivy:publish task or as a pattern token for use in resolvers (as raised in ivy-user list here: With configurations being
such a key component of ivy, it would be nice if the [conf] pattern were better supported
across different filtering processes. 

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message