Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [m2e-dev] m2e 0.12.2 not adding generated-sources
I'm not familiar with the code, but my guess is that m2e 0.12 can't know the output directory for every source generator from the pom, and it assumes the project has not been built prior to import.  Presumably when Update Configuration is called m2e just blindly adds folders in target/generated-sources/ to the Eclipse build path.

Matthew

On 10 August 2011 13:05, Derek Lewis <derek@xxxxxxxxxx> wrote:
Thanks for the response Igor.  I'm a bit confused though.

When you say m2e-core doesn't support code generation maven plugins, I understand that it doesn't actually execute the code generation without additional Eclipse plugins.  Doesn't it at least add target/generates-sources/foo to the source paths in Eclipse though?  The bit that is puzzling me, with 0.12.2, is that when I import the projects, the generated-sources aren't added to the source paths, but when I tell maven to "Update Project Configurations", it does add generated-sources.  This is all after having done a "mvn install" on the command line before importing.

So, in short:  Why does "Update Project Configurations" add the generated-sources to the build path, but importing the project doesn't.  That's the part that feels like a bug to me.  Does that work differently in 1.0?

Cheers,
Derek


On Tue, Aug 9, 2011 at 7:42 PM, Igor Fedorenko <igor@xxxxxxxxxxxxxx> wrote:
Although m2e-core 1.0 does not directly support any code generation
maven plugin, I believe jaxb and javacc are supported by m2e extensions
available from m2e marketplace.

Mapping of Maven project configuration to Eclipse workspace has been
significantly reworked in 1.0 and these changes cannot be backported to
0.12.x. [1] provides some background information about this change.

[1] http://wiki.eclipse.org/M2E_plugin_execution_not_covered

--
Regards,
Igor


On 11-08-10 3:43 AM, Derek Lewis wrote:
Hello,

I've been working a lot in recent months on getting our application
working smoothly in Eclipse 3.6 with Maven3 and M2Eclipse.  We've been
using m2e 0.12.x, since this seemed like the best choice when we started
the conversion from Ant to Maven, many months ago.  I'm having a fairly
significant problem with it though.  When I import any project than
generates sources (JAXB, JavaCC, etc) m2e doesn't add the generated
sources folder as a source folder until I do "Maven -> Update Project
Configuration".  Since we have 68 projects, 4 of which have generated
sources, I'd rather not have to document this as a manual step to
perform after "Import Existing Maven Project" when setting up a
development environment.  I'm using m2e 0.12.2.20110215-2017 from
https://repository.sonatype.org/content/sites/forge-sites/m2e/0.12.2/S/0.12.2.20110415-2017/.

I would like to upgrade to m2e 1.0 eventually, but we have a lot of
custom plugins that we would have to change to use the new org.eclipse
rather than org.maven packages, which we don't have the time to properly
test right now.  I'd really like to get this working on 0.12.2.  Is this
problem fixed on 1.0?  Is it possible to get a backport of the fix to 0.12?

Cheers,
Derek


_______________________________________________
m2e-dev mailing list
m2e-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-dev
_______________________________________________
m2e-dev mailing list
m2e-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-dev


_______________________________________________
m2e-dev mailing list
m2e-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-dev


Back to the top