Hello, Most likely the source directory is (incorrectly) overwritten at the compile plugin (or it is compiled by the parent pom or some other strange mechanisms like an ant plugin). The -X output (together with the effective pom) should tell you that as well.
Removing the <sourceDirectory>, moving the files to src/main/java and removing all properties or compile plugin options would be the proper cleanup action to plan for the long run ,) -- http://bernd.eckenfels.net -----Original Message----- From: "David M. Karr" <[email protected]> To: Maven Users List <[email protected]> Sent: Fr., 15 Jan. 2016 1:32 Subject: Re: Why is checkstyle failing on one project, but not others? Ok, that gave me a big clue, and a new question. I've realized that ALL of these projects are using "src" as their source root, instead of "src/main/java", but this one that is failing is the only one that specifies the "sourceDirectory" value. Those projects that aren't specifying the value are building just fine. Is Maven just guessing "I must have meant 'src'" and just using what it found? On 01/14/2016 04:15 PM, [email protected] wrote: > Hello, > > You can run the build with -X it will give you the actual config parameters > used for the plugin (especially includes/excludes/sourceDirectory) as well as > a list of the (not) scanned resources. > > Gruss > Bernd > --------------------------------------------------------------------- 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]
