Thanks Bobby and Alejandro for your inputs.
> > Please open a JIRA to follow up with this. Note that is not only in
> common
> > that code is generated, but in mapreduce as well. And there are
> different
> > things being generated, avro, protobuf, etc.
Filed a new JIRA for this issue
https://iss
Sorry that was a different page I looked at before going to the JIRA.
It said that we can manually add in the target/generated-test-source/java
directory as a source directory with something like
target/generated-test-source/java/**/*.java
I have no idea if it will work, but it looked cleaner t
Bobby,
What is the POM change you are referring to?
Thanks.
Alejandro
On Tue, Sep 20, 2011 at 7:00 AM, Robert Evans wrote:
> This is a known issue with the eclipse maven mojo
>
> http://jira.codehaus.org/browse/MECLIPSE-37
>
> The JIRA also describes a workaround, add the generated tests dir
This is a known issue with the eclipse maven mojo
http://jira.codehaus.org/browse/MECLIPSE-37
The JIRA also describes a workaround, add the generated tests directory in the
eclipse config with a pom change, which I think would be better then trying to
move the phase where test code is generate
Laxman,
This is not an incorrect usage of maven phases, those generated Java classes
are test classes, thus is generation in the 'generate-test-sources' phase.
The problem seem to be that eclipse does not recognize the
target/generated-test-source/java directory as a source directory (for
example
Hi All,
I can see lot of compilation issues after setting up my development
environment using "mvn eclipse:eclipse".
All these compilation issues are resolved after adding
"target/generated-test-sources" as a source folder to the common project.
When verified the "pom.xml", it's noticed th
