Hi,
Use the *build* *helper* *plugin* to add additional source paths
http://mojo.codehaus.org/*build*-*helper*-maven-*plugin*/http://mojo.codehaus.org/build-helper-maven-plugin/
cf.
http://www.nabble.com/Second-source-directory-for-generated-code-to6446457s177.html#a6446995
Rémy
Thanks guys. I've already got it working with the build helper plugin, but
was hoping there was some convention i could use to avoid it. Hopefully the
maven guys move to add one eventually.
On Dec 20, 2007 8:15 AM, Rémy Sanlaville [EMAIL PROTECTED] wrote:
Hi,
Use the *build* *helper* *plugin*
The convention is useful for the IDE integration that can check that
target/generated-sources subfolders and add them to source path without
actually requiring to build the project.
Milos
On Dec 20, 2007 2:43 PM, Kallin Nagelberg [EMAIL PROTECTED]
wrote:
Thanks guys. I've already got it
The eclipse plugin (not sure other IDE-plugins do same) will run a pre-build
(generate-resources phase) to let all code-generator declare
compileSourceRoots. This also aplies to maven-helper-plugin.
Based on this you MAY use whatever generate folder you like. The
convention is to use
at least the netbeans ide plugin will not run any phases when opening a
project. it relies solely on the convention. Ideally the plugin description
would include a marker on mojo parameters that make a generated source root
directory. That way one can check the actual location without running the
I'm working on such a mojo API extension (or anything else) to fix this
issue with the eclipse plugin. @see my post on [EMAIL PROTECTED]
Nico.
2007/12/20, Milos Kleint [EMAIL PROTECTED]:
at least the netbeans ide plugin will not run any phases when opening a
project. it relies solely on the
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;
/**
*
