[
https://issues.apache.org/jira/browse/MRELEASE-915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14632789#comment-14632789
]
Martin Gainty commented on MRELEASE-915:
----------------------------------------
possible scenario is you work in a body shop where all packages are generated
by outsourcers?
The build engineer requires Java Classes created from client-supplied XML
document template.
The build-engineer implements addCompileSourceRoot as generated-sources
location from jaxb
https://github.com/highsource/maven-jaxb2-plugin/wiki/Controlling-the-Output
But in verify phase when checkstyle is executed you see warnings from the jaxb
generated addCompileSourceRoot folder . Engineer knows that none of the code
outsourcers created this code since the folder name is not the typical gov.
package spec that outsources use. build-engineer wants checkstyle to bypass
scanning additional source directories such as the generated source directory
not specifically located in sourceDirectories attribute of
maven-checkstyle-plugin
Am i picturing the scenario accurately?
If so I can take a look at crafting an q&d algo which will bypass all source
directories not specified in sourceDirectories as I have some free time this
week.
Thanks,
Martin
> 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)
