[
https://issues.apache.org/jira/browse/IVY-208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gintas Grigelionis updated IVY-208:
-----------------------------------
Description:
I think it's important to separate the following two errors:
1. Unresolved dependency
2. Unknown configuration
These are two completely different errors, and the caller should have the
ability to treat them
different. For example, if my ivy file has two configurations defined:
compile
test
And I ask ivy to resolve the configuration "foo", I should be able tell ivy
that i really don't care
if "foo" doesn't exist. If i try to get a fileset from it later, i'll just get
an empty one.
Right now, it fails just as if some jar in the "compile" configuration couldn't
be found.
I will look at the code, to see how easy it would be to do this.
was:
I think it's important to seperate the following two errors:
1. Unresolved dependency
2. Unknown configuration
These are two completely different errors, and the caller should have the
ability to treat them
different. For example, if my ivy file has two configurations defined:
compile
test
And I ask ivy to resolve the configuration "foo", I should be able tell ivy
that i really don't care
if "foo" doesn't exist. If i try to get a fileset from it later, i'll just get
an empty one.
Right now, it fails just as if some jar in the "compile" configuration couldn't
be found.
I will look at the code, to see how easy it would be to do this.
> Separate dependency download failure from unknown configuration failure
> -----------------------------------------------------------------------
>
> Key: IVY-208
> URL: https://issues.apache.org/jira/browse/IVY-208
> Project: Ivy
> Issue Type: New Feature
> Components: Core
> Affects Versions: 1.3.1
> Reporter: Matt Inger
>
> I think it's important to separate the following two errors:
> 1. Unresolved dependency
> 2. Unknown configuration
> These are two completely different errors, and the caller should have the
> ability to treat them
> different. For example, if my ivy file has two configurations defined:
> compile
> test
> And I ask ivy to resolve the configuration "foo", I should be able tell ivy
> that i really don't care
> if "foo" doesn't exist. If i try to get a fileset from it later, i'll just
> get an empty one.
> Right now, it fails just as if some jar in the "compile" configuration
> couldn't be found.
> I will look at the code, to see how easy it would be to do this.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
