Yes, it's to do with the forked execution. I've made a test case and
created https://issues.apache.org/jira/browse/MRELEASE-915.
I haven't tried the yet, I will in a moment and
annotate the JIRA.
On Sun, Jul 12, 2015 at 1:08 PM, Benson Margulies wrote:
> On Sat, Jul 11, 2015 at 5:04 AM, Robert
On Sat, Jul 11, 2015 at 5:04 AM, Robert Scholte 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 y
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?
forked-path
thank
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.:
On Thu, Jul 9, 2015 at 8:04 PM, Benson Margulies
wrote:
> Ever since we bumped to 2.15 of the plugin, we've been hitting a
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
