On 22/03/06, Wayne Fay <[EMAIL PROTECTED]> wrote:
> I would think this might be addressed in the future when
> <provides>{interface}</provides> or something similar is added to
> Maven pom.
>
> Thus you could say in your jetty6 pom:
> <dep><implements>javax.logging</implements></dep>
>
> Then in the project pom:
> <dep>...log4j...<provides>javax.logging</provides></dep>
>
> Another perhaps more concrete example is javax.mail API and
> implementation. Sun created it originally but has a Sun Binary License
> so we can't distribute it in Maven repo. Projects Geronimo, Glassfish,
> and GNU Classpath all have their own versions of the javax.mail API.
> Ideally we could say in a pom "give me javax.mail, implementation 1.2
> or higher from someone" and then in another pom that depends on it, we
> could include "this is glassfish-mail.jar which implements the
> javax.mail 1.3 API" which would satisfy the dependency.
>
> I am fairly certain the Maven team knows about this use case and is
> actively working to design and implement a solution for it.Yep, this kinda thing is scheduled for 2.1: http://docs.codehaus.org/display/MAVEN/Specification+Dependencies+Design Although a plugin exclusions block would provide a parallel to how this situation is normally solve with regular project dependencies in 2.0. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
