[
http://jira.codehaus.org/browse/MOJO-1445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=226695#action_226695
]
Robert Scholte commented on MOJO-1445:
--------------------------------------
It's kind of weird to run jalopy over generated code, unless this code is
published or something, but even than... But I can think of another reason to
change this: it is possible for a Maven project to have multiple
sourceDirectories besides the generated ones (with a little help from
build-helper-maven-plugin).
It's should be quite easy to run jalopy over all available
(test)sourceDirectories, but that's maybe a bit too much.
> Make sourceDirectory and testSourceDirectory configurable
> ---------------------------------------------------------
>
> Key: MOJO-1445
> URL: http://jira.codehaus.org/browse/MOJO-1445
> Project: Mojo
> Issue Type: Improvement
> Components: jalopy
> Reporter: Andreas Sewe
> Priority: Minor
>
> This would be tremendously useful for generated sources which often should
> not end up in {{${project.build.sourceDirectory}}}; the
> {{javacc-maven-plugin}}, e.g., outputs its generated sources (which could
> benefit from reformating) to
> {{${project.build.directory}/generated-sources/javacc}}.
--
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
