[
https://issues.apache.org/jira/browse/IVY-472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12553729
]
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:
<resolvers>
<sftp name="remote">
<ivy pattern="sftp://user:[EMAIL
PROTECTED]:port/repository/[module]/[conf]/[module]-[revision]-[branch].xml"/>
<artifact pattern="sftp://user:[EMAIL
PROTECTED]:port/repository/[module]/[conf]/[artifact]-[revision]-[branch].[ext]"/>
</sftp>
</resolvers>
b. Our ivy file:
<publications>
<artifact name="IvyTest" type="dll" ext="dll" conf="net11" />
<artifact name="IvyTest" type="dll" ext="dll" conf="net20" />
</publications>
c. And our publish commands:
<target name="publish-net11" depends="build-net11">
<ivy:publish resolver="remote" conf="net11"
pubrevision="1.2.3.4" overwrite="true"
artifactspattern="${basedir}/build/net11/[artifact].[ext]" />
</target>
<target name="publish-net20" depends="build-net20">
<ivy:publish resolver="remote" conf="net20"
pubrevision="1.2.3.4" overwrite="true"
artifactspattern="${basedir}/build/net20/[artifact].[ext]" />
</target>
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: https://issues.apache.org/jira/browse/IVY-472
> 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:
> http://www.nabble.com/publishing-configurations-tf3555931.html). 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.
