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 .equals(..).
-john
On Jun 8, 2007, at 10:48 AM, Mark Hobson wrote:
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 - anyone got an opinion
whether this is right or wrong?
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---
John Casey
Committer and PMC Member, Apache Maven
mail: jdcasey at commonjava dot org
blog: http://www.ejlife.net/blogs/john
