ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexey Kiselev (JIRA)" <>
Subject [jira] Commented: (IVY-472) conf not supported as pattern filtering token
Date Thu, 20 Dec 2007 17:34:43 GMT


Alexey Kiselev commented on IVY-472:

We're .Net developers. We want to bo be allowed to compile different dll's with exaclty the
same names under different platform. These platforms may be .Net 1.1, .Net 2.0 or Mono and
so on. For example look at log4net project. 
We want to distiguish published artifacts trough Ivy configurations mechanism.

The example:
a. Our ivy settings file:
        <sftp name="remote">
            <ivy pattern="sftp://user:password@host:port/repository/[module]/[conf]/[module]-[revision]-[branch].xml"/>
            <artifact pattern="sftp://user:password@host:port/repository/[module]/[conf]/[artifact]-[revision]-[branch].[ext]"/>
b. Our ivy file:
		<artifact name="IvyTest" type="dll" ext="dll" conf="net11" />
		<artifact name="IvyTest" type="dll" ext="dll" conf="net20" />
c. And our publish commands:
	<target name="publish-net11" depends="build-net11">
		<ivy:publish resolver="remote" conf="net11" pubrevision="" overwrite="true" artifactspattern="${basedir}/build/net11/[artifact].[ext]"
	<target name="publish-net20" depends="build-net20">
		<ivy:publish resolver="remote" conf="net20" pubrevision="" overwrite="true" artifactspattern="${basedir}/build/net20/[artifact].[ext]"

It is really a point for us, that we can have two binary assemblies, which are distinguish
by it's binary content rather than by it's names.

> 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