> Test was only an example... in ivy, configurations are not limited > (you can use the name you want), and we assume nothing about their > transitivity. It's the developer who choose, by describing its > configurations mapping: in my "buildtime" I need xdoclet "runtime", > for example. So I can also say that in my conf "test" I need this > component "test" configuration. It's very flexible, and we answer to > many different needs with that.
There is no need for build time as it is all done via plugins and is separate in Maven. We have runtime, which is used for distribution purposes, as well as tests, and we have the default compile. > > Is this (or will it be) possible with m2 ? There's a chance we'll add more later, or make it arbitrary if we introduce arbitrary classpaths. This would probably come with additional lifecycle phases - but I see little need for it. What other types of dependencies do you see than compile, runtime and test? Maybe integration test, when we have that, though most plugins will just select dependencies from the existing ones, and filters can be used to pick up the rare special case. Too much flexibility is not always a good thing, because when it is unnecessary it usually comes with added complexity. - Brett --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
