Kallin,
You need to tell Maven that the location of your generated source should
be included as part of the build. Ie
/**
* @parameter default-value="${project}"
* @required
* @readonly
*/
private MavenProject project;
/**
* @parameter
default-value="${project.build.directory}/generated-sources/myPluginId"
* @required
* @readonly
*/
private File sourceDirectoryPath;
...
project.addCompileSourceRoot(sourceDirectoryPath);
Have a read of "Better builds with Maven" page 148.
William
> -----Original Message-----
> From: Kallin Nagelberg [mailto:[EMAIL PROTECTED]
> Sent: Thursday, 20 December 2007 2:18 PM
> To: users@maven.apache.org
> Subject: [***POSSIBLE SPAM***] - generated sources convention
> - Sender is forged (SPF Fail)
>
> I'm working on adapting some source generation code into the
> maven lifecycle. I've written a plugin that is generating the
> sources (albeit at random places) and bound it to the
> generate sources phase.
> I've read in a couple places that the standard location is
> target/generated-sources/<plugin-id>. However, the compiler
> plugin doesn't check this directory. I could always just
> ensure these directories are explicitly added for
> compilation, but I wanted to check if there was any
> convention (besides generating into src/main/java) that would
> allow the compilation to occur automatically.
>
> Thanks
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
