Nigel Magnay wrote: > Yes. It's horrible. It occurs in other places too -- for example, in > environments such as flex, you can declare a dependency with more scopes > than java (merged, internal, external, rsl or caching). If it's an RSL, > then you may choose one of about 4 'application domains' that control how > it will be shared. > > The scope bit sort of works (maven moans about it, and claims it's all > unsupported
what's unclear about this bit then? > , and transitive dependencies declared with nonstandard scopes > don't work properly). The application domains - well, you're left > duplicating almost all of the dependency information somewhere else in the > POM. Which, as you say, is tedious, and gets out of sync. > > I ended up writing a 'pom pre-processor xslt' that allowed me to include > elements in exactly the way you're describing to at least maintain some > kind DRY sanity. It's one of the thinks I look at gradle for, and wonder > if that might be a better choice. Sorry, but it seems to me that it was simply a wrong approach to define own scopes. You run Maven in an undefined state and moan about it's undefined behavior. Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
