On 5/17/05, Peter van de Hoef <[EMAIL PROTECTED]> wrote: > Why are built-in plugins inherited and user-defined plugins not? (their usage > is not inherited, their configuration is > via <pluginManagement> but their usage has to be specified in each project).
Neither are. There is no such thing as a "built-in" plugin. What does happen, is that certain goals are preconfigured, and that discovers those plugins... so if you call "aspectj:aspectj", it will work immediately. But you are going to need to configure it on the projects that use it. So what you are saying is that you want to be able to inherit the enablement of aspectj on every project inheriting a certain POM. This isn't a use case we've considered (again, we want inheritence and master build to co-exist in m2, which is why active parts of the pom are not inherited, only configuration). I'll keep it in mind. - Brett --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
