error messages not wanted

[scast...@lgc.com]

It looks like ivysvn produces error messages when an artifact can NOT
be found in the ivysvn resolver. These error messages should NOT
occur since this is a NORMAL occurrence. If I use a chained resolver,
then the desired artifact will be searched in all resolvers in my
chain before picking the best one. Therefore, it needs to be able to
search the ivysvn resolver and NOT find it and NOT throw an error
message.

My users will think the build is not working properly if they start
seeing error messages from ivysvn when there really is no error.

[Xavier Hanin]

On Thu, Apr 9, 2009 at 9:52 PM, <scast...@lgc.com> wrote:

It looks like ivysvn produces error messages when an artifact can NOT
be found in the ivysvn resolver.  These error messages should NOT
occur since this is a NORMAL occurrence.  If I use a chained resolver,
then the desired artifact will be searched in all resolvers in my
chain before picking the best one.  Therefore, it needs to be able to
search the ivysvn resolver and NOT find it and NOT throw an error
message.

I second this opinion, despite I find it "just" annoying, I think IvySvn shouldn't consider an artifact not found as an error.

 

Xavier

 

My users will think the build is not working properly if they start
seeing error messages from ivysvn when there really is no error.

Blogger - http://xhab.blogspot.com/
Apache Ivy Creator - http://ant.apache.org/ivy/

[Adrian Woodhead]

In our case seeing as we only use the IvySvnResolver (no chaining) it
actually is an error as it means someone is trying to retrieve an
artifact which doesn't exist. But I see your point when it comes to
using chained resolvers and I will look into making the IvySvnResolver
behave more like the FileResolver in this regard.

Adrian

[Adrian Woodhead]

OK, I have added this as an issue:

http://code.google.com/p/ivysvn/issues/detail?id=21

Further discussion will continue there.

2009/4/17 Adrian Woodhead <adr...@last.fm>