Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 347458 - [mojo] antlr configuration is not compatible with latest m2e
Summary: [mojo] antlr configuration is not compatible with latest m2e
Status: RESOLVED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: m2e (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-27 10:00 EDT by Igor Fedorenko CLA
Modified: 2021-04-19 13:27 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Igor Fedorenko CLA 2011-05-27 10:00:40 EDT
from http://dev.eclipse.org/mhonarc/lists/m2e-users/msg00575.html

<quote>
I'm using M2E 0.13.0.201105171436 with Eclipse 3.7 RC1. I'm trying to import a project that uses the ANTLR3 plugin (see attached test project). M2E offers to download the antlr3 project configurator, but then I get the following exception during import:

java.lang.IncompatibleClassChangeError: Expecting non-static method org.eclipse.m2e.core.MavenPlugin.getMaven()Lorg/eclipse/m2e/core/embedder/IMaven;
at org.sonatype.m2e.antlr.internal.AntlrBuildParticipant.build(AntlrBuildParticipant.java:36)
at org.eclipse.m2e.core.internal.builder.MavenBuilder.build(MavenBuilder.java:179)
at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:728)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239)
at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295)
at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351)
at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:374)
at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143)
at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
</quote>
Comment 1 Jochen Wiedmann CLA 2011-05-27 16:53:16 EDT
Confirming the same problem here.
Comment 2 Igor Fedorenko CLA 2011-05-30 07:47:06 EDT
I have a possible fix available from https://repository.sonatype.org/content/repositories/forge-sites/m2e-extras/0.13.0/N/0.13.0.201105271033/

To try, you need to uninstall ANTLR project configurator first, then install "Project configurators for some commonly used maven plugins." from the update site above.

Let us know if the new version works proper and we'll push it to m2e marketplace if it does.
Comment 3 Jochen Wiedmann CLA 2011-05-30 08:12:46 EDT
I had to deinstall the buildhelper connector as well, but apart from that it looks good.
Comment 4 Lóránt Pintér CLA 2011-05-30 08:36:10 EDT
I had to upgrade the buildhelper as well, but apart from that, it works great. Thanks for the quick fix!
Comment 5 Igor Fedorenko CLA 2011-05-30 09:18:42 EDT
Now is the trick question -- can somebody explain why the project attached to [1] still fails, albeit differently?

[1]  http://dev.eclipse.org/mhonarc/lists/m2e-users/msg00575.html
Comment 6 Jochen Wiedmann CLA 2011-05-30 10:00:36 EDT
The first question would possibly be: How "differently"?
Comment 7 Igor Fedorenko CLA 2011-06-06 10:23:58 EDT
m2e generates classes until "null" package name and the project ends up with red markers. build from command line works, so I assume m2e uses wrong generation output folder, at least for some projects.
Comment 8 Igor Fedorenko CLA 2011-06-06 10:27:25 EDT
(In reply to comment #7)
> m2e generates classes until "null" package name and the project ends up with
> red markers. build from command line works, so I assume m2e uses wrong
> generation output folder, at least for some projects.

to clarify, m2e generates classes inside directory with "null" name inside java sources folder.
Comment 9 Igor Fedorenko CLA 2011-06-25 23:39:11 EDT
please reopen if you still have problems with m2e/antlr code generation support in m2e 1.0.0
Comment 10 Denis Roy CLA 2021-04-19 13:27:02 EDT
Moved to https://github.com/eclipse-m2e/m2e-core/issues/