On Sat, Jul 11, 2015 at 5:04 AM, Robert Scholte <[email protected]> wrote: > You know that release:perform doesn't do any magic. It would be the same as: > cd target/checkout > mvn deploy (or mvn deploy site-deploy) > > If this works as expected (without failures), then it looks like something > is leaking. > Could you try to switch to the ForkedMavenExecutor? > <mavenExecutorId>forked-path</mavenExecutorId>
Where do I put that? release plugin config? > > thanks, > Robert > > Op Fri, 10 Jul 2015 03:04:55 +0200 schreef Benson Margulies > <[email protected]>: > >> 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: [email protected] >> For additional commands, e-mail: [email protected] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
