>As for detecting >project-state changes in the plugin itself (or the POM, as Brian asked >about) we'd have to scan the entire logic of the mojo (and classes it >used) to see whether any of it modified the project/model graph...which
>is obviously waaaay too heavy to do at runtime. Actually what I meant is a hackish scanning of a parameter in the mojo config in the pom, something like: <configuration> <affectsBuild>true</affectsBuild> </configuration> Basically a field unused by the plugins that we could see in the pom. Obviously not the greatest but it could work. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
