We hadn't planned to overload scope like this, and for similar reasons to not adding properties - they don't hold up under transitivity because it requires that the dependency knows something about the final project, which is impossible.
The scope provides a sensible default for most operations (by separating into the 3 groups), and from there we apply filters to modify that as necessary which can be part of the plugin configuration. Do you have a use case for selection of particular dependencies that doesn't match any of the scopes? Cheers, Brett Juraj Burian wrote: > Rafal Krzewski wrote: > >> Juraj Burian wrote: >> >>> We are working on jboss-aop & APT plugins implementation. >>> We encountered the folowing problem (in general): >>> We need to split classpath into several parts. In other words, we >>> need to group dependencies. >>> >>> For example, when running JBoss AOP it is necessary to supply >>> classpath where aspects are found and a different classpath where >>> classes that should be weaved are (ie. 2 different classpath). >> >> >> >> It occured to me that M2 has already a notion of dependency grouping >> and separate classpaths, determined by "dependency scope" there is >> "compile" scope and "test" scope. Maybe you need to define additional >> scopes, like compile-aspectpath, compile-inpath (or -weavepath), >> test-aspectpath and so on? And how would these relate to dependency >> inheritance (transitiveness)? >> >> R. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> > Right, it's possible solution, but every new plugin will need a new > scope definition => lot of related changes in maven "core". > Dependency "transitivity" (bug is there) is managed via <optional> > flag (only scope:provided is by default not transitive), but in > general it depends on purpose of the given classpath. > > JuBu > > > --------------------------------------------------------------------- > 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]
