I'm pretty sure I just wrapped the core artifactsFilter impl so that I could deal with the collection. In any case that I can, I try to use the core functionality but sometimes I wrap it to do any additional work needed. This was done mainly because mdep started out at Mojo and I didn't have Karma to influence core.
-----Original Message----- From: Mark Hobson [mailto:[EMAIL PROTECTED] Sent: Monday, June 18, 2007 8:53 AM To: Maven Developers List Subject: Re: Adding wildcards to IncludesArtifactFilter Hi Brian, On 15/06/07, Brian E. Fox <[EMAIL PROTECTED]> wrote: > Mark, > There are already a bunch of filters defined within dependency for a lot > of this. None of them work for you or is it that you need to access them > from the shared component? I did see them, although they weren't really what I was looking for. How come you needed to introduce a new interface ArtifactsFilter rather than reuse the existing ArtifactFilter API? I need a filter that supports wildcards on groupId, artifactId, type and version together, whereas the ArtifactsFilter implementations look for equality or startsWith on only one part. I also deal with an artifact at a time, whereas the ArtifactsFilter API looks more suitable for dealing with collections of artifacts. Cheers, Mark --------------------------------------------------------------------- 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]
