Community
Participate
Working Groups
In older versions of m2e, updating the project configuration would automatically add the generated-sources folder as an Eclipse source folder if it existed. In 1.0, it refuses to add the folder, and ejects it if it was previously added. I believe the previous behavior is correct.
See [1] for description of expected behaviour and [2] for explanation how to add support for a code generation maven plugin. [1] http://wiki.eclipse.org/M2E_plugin_execution_not_covered [2] http://wiki.eclipse.org/M2E_Extension_Development
I've read that before, but it's not what I'm talking about. I understand if I want my generator to run automatically, I need to implement the special code. All I'm saying is, if I run my generator manually (via tha Run menu) and then do "Update Project Configuration," I'd like for M2E to recognize that directory and use it as a source folder.
There is no way to find generated sources folder(s) without executing maven plugin that generates the code.
I guess I don't understand that limitation. Is that just because of the way the m2e plugin is structured, or is there some other eclipse limitation there?
This has nothing to do with eclipse. pom.xml does not have information about generated sources folder, so even if the folder exists on filesystem there is no (reliable) way to find it there.
So... how did the older version of m2e detect the generated sources folder automatically? Maven plugins that generate sources generally register those source trees with the maven runtime (or their users use the maven-buildhelper-plugin). That is certainly not part of the pom.xml, but is that something available dynamically?
Oops. I apologize. My question is answered in the prior links.
*** Bug 372847 has been marked as a duplicate of this bug. ***
Moved to https://github.com/eclipse-m2e/m2e-core/issues/
