[
https://issues.apache.org/jira/browse/FLUME-2009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13642730#comment-13642730
]
Thiruvalluvan M. G. commented on FLUME-2009:
--------------------------------------------
You have to manually add the source folder(s) for generated classes to the
project. I'm sorry I missed to document it.
To do this, for each (sub) project in the project preferences (or properties in
some platforms), select "Java Build Path" and within that "Source" tab. Then
click on the "Add folder" and add the folder where the code is generated, which
is invariably a folder under "target/generated-sources". This needs to be done
once for the workspace. After this you can delete the projects from the
workspace and reimport any number of times. You don't have to repeat this step.
The reason why this cannot be automated is this: Maven plugins that generate
code automatically add the directory where the code is generated to the source
path in to the in-memory Project option. That is, the in-memory version of POM
gets modified on the fly in the "generate-sources" phase, which gets used in
the later phases. But, M2e looks at the static pom.xml and imports the source
paths. So the dynamic folders do not show up there.
> Flume project throws error when imported into Eclipse IDE (Juno)
> ----------------------------------------------------------------
>
> Key: FLUME-2009
> URL: https://issues.apache.org/jira/browse/FLUME-2009
> Project: Flume
> Issue Type: Improvement
> Components: Build
> Affects Versions: v1.3.1
> Reporter: Thiruvalluvan M. G.
> Assignee: Thiruvalluvan M. G.
> Attachments: FLUME-2009.patch
>
>
> It happens because Eclipse's M2E (maven integration) does not know what to do
> when certain plugins are executed. The forthcoming patch fixes the problem.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
