[
https://issues.apache.org/jira/browse/MRELEASE-915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14632913#comment-14632913
]
Benson Margulies commented on MRELEASE-915:
-------------------------------------------
Martin, the scenario you describe bears no resemblance to the situation at
hand. I wrote a maven plugin which generates code from an XML file and a
template. The code in question is not intended to comply with our checkstyle
rules. I have worked around it by configuring checkstyle to look only in
src/main/java. I'd like to see someone track this down in the release plugin or
the core; I'm not sure where to start or I'd do some tracking on my own.
> Forked execution of perform leaks source roots
> ----------------------------------------------
>
> Key: MRELEASE-915
> URL: https://issues.apache.org/jira/browse/MRELEASE-915
> Project: Maven Release Plugin
> Issue Type: Bug
> Components: perform
> Affects Versions: 2.5.1
> Reporter: Benson Margulies
>
> https://github.com/bimargulies/release-root-leakage is a test case for the
> following:
> If you add a source root in generate-sources in a pom, that source root will
> show up in the 'validate' phase in the forked execution for release:perform.
> This causes checkstyle to see things that it should not, if nothing else bad.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
