[
https://issues.apache.org/jira/browse/IVY-403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gintas Grigelionis updated IVY-403:
-----------------------------------
Description:
Say my project depends on some module in my ivy repository and when I specifies
the dependency, I use the following:
{code:xml}
<dependency org="org" name="module" rev="1.0.1" />
{code}
so no "conf" attribute is specified. Currently in version 1.3.1 and 1.4 I
believe, the behavior is that all the public configurations of the module in
ivy repository will be used, which is not the desired behavior sometimes. I'd
like to have a way to change this default behavior so that when no "conf" is
specified, it only uses a specific public configuration.
e.g.
Module in ivy repository has the following configurations:
{code:xml}
<configurations>
<conf name="core" />
<conf name="jms" />
<conf name="swing-gui" />
</configurations>
{code}
And in my project, when I specify:
{code:xml}
<dependency org="org" name="module" rev="1.0.0" />
{code}
only the "core" configuration is used. And when I specify:a
{code:xml}
<dependency org="org" name="module" rev="1.0.0" conf="jms" />
{code}
only "jms" configuration is used.
was:
Say my project depends on some module in my ivy repository and when I specifies
the dependency, I use the following:
<dependency org="org" name="module" rev="1.0.1" />
so no "conf" attribute is specified. Currently in version 1.3.1 and 1.4 I
believe, the behavior is that all the public configurations of the module in
ivy repository will be used, which is not the desired behavior sometimes. I'd
like to have a way to change this default behavior so that when no "conf" is
specified, it only uses a specific public configuration.
e.g.
Module in ivy repository has the following configurations:
<configurations>
<conf name="core" />
<conf name="jms" />
<conf name="swing-gui" />
</configurations>
And in my project, when I specify:
<dependency org="org" name="module" rev="1.0.0" />
only the "core" configuration is used. And when I specify:a
<dependency org="org" name="module" rev="1.0.0" conf="jms" />
only "jms" configuration is used.
> Customize "default" conf behavior
> ---------------------------------
>
> Key: IVY-403
> URL: https://issues.apache.org/jira/browse/IVY-403
> Project: Ivy
> Issue Type: New Feature
> Components: Ant
> Affects Versions: 1.3.1
> Environment: Windows xp, Linux, Solaris, Unix
> Reporter: Han Wang
> Priority: Minor
>
> Say my project depends on some module in my ivy repository and when I
> specifies the dependency, I use the following:
> {code:xml}
> <dependency org="org" name="module" rev="1.0.1" />
> {code}
> so no "conf" attribute is specified. Currently in version 1.3.1 and 1.4 I
> believe, the behavior is that all the public configurations of the module in
> ivy repository will be used, which is not the desired behavior sometimes. I'd
> like to have a way to change this default behavior so that when no "conf" is
> specified, it only uses a specific public configuration.
> e.g.
> Module in ivy repository has the following configurations:
> {code:xml}
> <configurations>
> <conf name="core" />
> <conf name="jms" />
> <conf name="swing-gui" />
> </configurations>
> {code}
> And in my project, when I specify:
> {code:xml}
> <dependency org="org" name="module" rev="1.0.0" />
> {code}
> only the "core" configuration is used. And when I specify:a
> {code:xml}
> <dependency org="org" name="module" rev="1.0.0" conf="jms" />
> {code}
> only "jms" configuration is used.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
