[
http://jira.codehaus.org/browse/MOJO-267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_99238
]
Corridor Software Developer commented on MOJO-267:
--------------------------------------------------
Most maven projects are single source tree oriented. If the code in other
locations tends to be generated, why reformat it? It won't ever be edited by
hand so asserting formatting rules upon it would just add to the build time for
effort which will be discarded on the next clean.
> use compileSourceRoots instead of sourceDirectory
> -------------------------------------------------
>
> Key: MOJO-267
> URL: http://jira.codehaus.org/browse/MOJO-267
> Project: Mojo
> Issue Type: Improvement
> Components: jalopy
> Environment: any
> Reporter: Stefan Hübner
> Priority: Minor
> Attachments: MOJO-267-jalopy-maven-plugin.patch
>
>
> Wouldn't it be useful beeing able to format not just sources contained in
> Maven's standard {{sourceDirectory}}? For instance when generating source
> code by some kind of generating tool, those sources likely won't go to
> {{sourceDirectory}}, but to something like {{target/generated-sources/..}}.
> (for instance).
> Since Maven's compiler-plugin compiles anything found in the
> *compileSourceRoots*-list, wouldn't that be a good idea for the Jalopy-plugin
> too?
> This would apply to *testCompileSourceRoots* accordingly.
> Regards,
> Stefan
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
