Use ${project.compileSourceRoots} as the default "sourcePath"

[GoogleCodeExporter]

for the flex-compiler-mojo, if unspecified, the "sourchPaths" defaults to 
${project.build.sourceDirectory}. This is this single-defined source path.

some plugins may generate source code, and it is common for them to append 
their generated 
source directory to the ${project.compileSourceRoots} list.

if unspecified, the default "sourcePath" should pull form 
${project.compileSourceRoots}, which will 
enable transparent operation with code generation plugins. otherwise the path 
to generated sources 
must be re-specified for every plugin (compiler, asdoc, etc)

Original issue reported on code.google.com by peter.royal@pobox.com on 29 Sep 2008 at 9:53

[GoogleCodeExporter]

compileSourceRoots can be changed by another plugins?

VELO

Original comment by velo...@gmail.com on 29 Sep 2008 at 9:59

[GoogleCodeExporter]

yup.

that's how the maven java compiler works. see

http://svn.apache.org/viewvc/maven/plugins/trunk/maven-compiler-
plugin/src/main/java/org/apache/maven/plugin/CompilerMojo.java?view=markup

the 'compileSourceRoots' member of the class. you should be able to get rid of 
the java code that sets up the 
source paths and just have maven inject the list for ya entirely.

Original comment by peter.royal@pobox.com on 29 Sep 2008 at 10:06

[GoogleCodeExporter]

Awesome.

I didn't notice that.

I will refactor compiler mojo ASAP.

VELO

Original comment by velo...@gmail.com on 29 Sep 2008 at 10:10

• Changed state: Accepted

[GoogleCodeExporter]

Fixed at revision 789

Original comment by velo...@gmail.com on 10 Oct 2008 at 12:42

• Changed state: Fixed