I don't know the answer to your intriguing question... my suggestion prevents the problem though: use Checkstyle suppression filters for the generated directories, e.g.: <suppress files="[\\/]generated-sources[\\/]" checks="[a-zA-Z0-9]*" />
On Thu, Jul 9, 2015 at 8:04 PM, Benson Margulies <bimargul...@gmail.com> wrote: > Ever since we bumped to 2.15 of the plugin, we've been hitting a > problem. I don't have a concise repro, so I'm not opening a JIRA yet, > but I thought I'd inquire for other people's experience. > > We use some source generators, and none of them generate source that > is acceptable to our checkstyle rules. To prevent checkstyle from > processing that stuff, we bind the 'check' goal to the validate phase. > Since this is before generate-sources, it comes and goes before the > generator plugin(s) have a chance to register any additional source > roots. > > The recent change afflicts only release builds. All is well until we > run release:perform, and then the build fails because of checkstyle > complaints on generated source. > > How is it that the release plugin causes the generated source roots to > be visible to the plugin? > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
