That's implementation specific, we're talking about an interface here. I don't see why we should take out this method. If someone wants to use it, fine. If not, also fine.
-----Original Message----- From: Oleg Gusakov [mailto:[EMAIL PROTECTED] Sent: Sunday, September 28, 2008 12:04 PM To: Maven Developers List Subject: Re: wagon's resourceExists() call efficiency ? But this information comes from repository metadata, not from probing the actual file. If it does - repository integrity is broken, isn't it? Deploy should read the metadata anyway as it is supposed to update [in a dumb http/dav repository, Nexus can do it for us], so if version is not in metadata, or metadata read failed it's equivalent to resource does not exist, but now you have much more information to act upon. Ralph Goers wrote: > Yes. I would actually like the deploy plugin to NOT deploy a > non-SNAPSHOT artifact if it is already there. > > Oleg Gusakov wrote: >> I cannot imagine a use case where you would check that artifact >> exists in the remote repository and then don't download it. Can you? >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
