On Fri, Jul 11, 2008 at 9:47 AM, Kristian Rink <[EMAIL PROTECTED]> wrote: > Folks; > > in my environment, I do have a parent pom all my projects do inherit > from. This parent pom is used, among other things, to keep global > dependencies. My question on that, however: Asides from declaring > dependencies which effectively state what is needed, is there a way to > also declare "global exclusions" to, regardless of artifacts included, > state what artifacts _not at all_ to include? > > To outline what I want: We do use slf4j for logging, along with > jcl-over-slf4j (briding commons-logging output to slf4j) or > log4j-over-slf4j (bridging log4j output to slf4j) so no matter what > happens I don't want to, say, have any artifact (Spring likes to do > this, in example...) pull commons-logging as a transitive dependency > simply because this is already satisfied by jcl-over-slf4j and would > just cause trouble. So far however I have to manually define an > exclusion to that for every required project and every dependency > manually which doesn't seem that comfortable a thing to do. Can this be > done somehow smarter? > > Thanks in advance, best regards. > Kristian
>From what I know this is not supported in Maven 2.0.x. You'll have to do the manual labour of specifying exclusions for every dependency which pulls in what you don't want. I think there's a jira for this somewhere which might be scheduled for 2.1. -- - Jan Fredrik Wedén --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
