> Either way, the project specific dependencies would not > need to be resolved until the proper plugin needed them. > The **:compile plugins would grab the build dependencies > plus whatever else it needed (like test dependencies for > the test:compile).
There may be plugins that fit into more than one of the "categories". For example, is multiproject a run-time, compile-time or test-time plugin? If you want to go this route, plugins should probably be considered compile-time by default, unless told otherwise. I think my earlier suggestion (which focuses on user-controlled goals rather then "third party" controlled plugins) is both easier and more workable. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
