| Summary: | [mojo] antlr configuration is not compatible with latest m2e | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Igor Fedorenko <igor> |
| Component: | m2e | Assignee: | Project Inbox <m2e.core-inbox> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | jochen.wiedmann, lptr |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
Igor Fedorenko
Confirming the same problem here. 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. I had to deinstall the buildhelper connector as well, but apart from that it looks good. I had to upgrade the buildhelper as well, but apart from that, it works great. Thanks for the quick fix! 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 The first question would possibly be: How "differently"? 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. (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. please reopen if you still have problems with m2e/antlr code generation support in m2e 1.0.0 |