[
https://issues.apache.org/jira/browse/IVY-1407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gintas Grigelionis updated IVY-1407:
------------------------------------
Description:
I noticed that when using the new <ivy:resolve> child elements that were
introduced in 2.3, classifier resolution no longer works. This is unfortunate
because having dependencies in the ant build.xml allowed for ant property
references to be used in the dependency declarations, which is really useful.
For example:
build.xml:
{code}
<ivy:resolve>
<dependency org="org.zeromq" name="jzmq" rev="${jzmq.version}">
<artifact name="jzmq" type="source" ext="jar" m:classifier="sources"/>
</dependency>
</ivy:resolve>
{code}
ivysettings.xml:
{code}
<ivysettings>
<settings defaultResolver="nexus" />
<resolvers>
<ibiblio name="nexus" m2compatible="true"
root="http://nexus.local:8082/nexus/content/groups/all";
pattern="[organisation]/[module]/[revision]/[artifact]-[revision](-[m:classifier]).[ext]">
</ibiblio>
</resolvers>
</ivysettings>
{code}
What winds up happening is that the *binary* jar is getting downloaded and
placed in the sources directory, instead of the source jar. It essentially
seems like the classifier parameter is not passed along to the resolver.
was:
I noticed that when using the new <ivy:resolve> child elements that were
introduced in 2.3, classifier resolution no longer works. This is unfortunate
because having dependencies in the ant build.xml allowed for ant property
references to be used in the dependency declarations, which is really useful.
For example:
build.xml:
<ivy:resolve>
<dependency org="org.zeromq" name="jzmq" rev="${jzmq.version}">
<artifact name="jzmq" type="source" ext="jar" m:classifier="sources"/>
</dependency>
</ivy:resolve>
ivysettings.xml:
<ivysettings>
<settings defaultResolver="nexus" />
<resolvers>
<ibiblio name="nexus" m2compatible="true"
root="http://nexus.local:8082/nexus/content/groups/all";
pattern="[organisation]/[module]/[revision]/[artifact]-[revision](-[m:classifier]).[ext]">
</ibiblio>
</resolvers>
</ivysettings>
What winds up happening is that the *binary* jar is getting downloaded and
placed in the sources directory, instead of the source jar. It essentially
seems like the classifier parameter is not passed along to the resolver.
> Classifiers not working with embedded ivy:resolve dependencies
> --------------------------------------------------------------
>
> Key: IVY-1407
> URL: https://issues.apache.org/jira/browse/IVY-1407
> Project: Ivy
> Issue Type: Bug
> Affects Versions: 2.3.0
> Reporter: Edwin Park
> Priority: Major
>
> I noticed that when using the new <ivy:resolve> child elements that were
> introduced in 2.3, classifier resolution no longer works. This is unfortunate
> because having dependencies in the ant build.xml allowed for ant property
> references to be used in the dependency declarations, which is really useful.
> For example:
> build.xml:
> {code}
> <ivy:resolve>
> <dependency org="org.zeromq" name="jzmq" rev="${jzmq.version}">
> <artifact name="jzmq" type="source" ext="jar" m:classifier="sources"/>
> </dependency>
> </ivy:resolve>
> {code}
> ivysettings.xml:
> {code}
> <ivysettings>
> <settings defaultResolver="nexus" />
> <resolvers>
> <ibiblio name="nexus" m2compatible="true"
> root="http://nexus.local:8082/nexus/content/groups/all";
>
> pattern="[organisation]/[module]/[revision]/[artifact]-[revision](-[m:classifier]).[ext]">
> </ibiblio>
> </resolvers>
> </ivysettings>
> {code}
> What winds up happening is that the *binary* jar is getting downloaded and
> placed in the sources directory, instead of the source jar. It essentially
> seems like the classifier parameter is not passed along to the resolver.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
