Re: DefaultArtifact.equals ignoring scope

On 08/06/07, John Casey <[EMAIL PROTECTED]> wrote: IMO, it's a representation of an artifact in the repository (or elsewhere)...scope is just a tag designating its use within the current build. Therefore, scope has nothing to do with whether two artifacts somewhere on the system are equal. So, I

Re: DefaultArtifact.equals ignoring scope

IMO, it's a representation of an artifact in the repository (or elsewhere)...scope is just a tag designating its use within the current build. Therefore, scope has nothing to do with whether two artifacts somewhere on the system are equal. So, I'd say it shouldn't incorporate scope in .equa

Re: DefaultArtifact.equals ignoring scope

On 18/01/07, Mark Hobson <[EMAIL PROTECTED]> wrote: Hi there, On my travels I noticed DefaultArtifact [1] equals and hashCode ignores scope - is that intentional? Could prove to be a problem when check to see if an artifact has moved scope. Just encountered this again whilst debugging - anyon

DefaultArtifact.equals ignoring scope

Hi there, On my travels I noticed DefaultArtifact [1] equals and hashCode ignores scope - is that intentional? Could prove to be a problem when check to see if an artifact has moved scope. Mark [1] http://svn.apache.org/repos/asf/maven/components/trunk/maven-artifact/src/main/java/org/apache/