Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 347708 - java nature doesn't appear on java project when another configurator is in the house
Summary: java nature doesn't appear on java project when another configurator is in th...
Status: CLOSED INVALID
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: m2e (show other bugs)
Version: unspecified   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-30 18:15 EDT by benson margulies CLA
Modified: 2021-04-19 13:21 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description benson margulies CLA 2011-05-30 18:15:22 EDT
git://github.com/bimargulies/m2e-groovy-0.13-attempt.git

is an m2e configurator plugin (a pure eclipse build)

If you install it, and try to import the project from:

git://github.com/bimargulies/m2e-groovy-configuration-test-project.git

there will be no java nature.

Without the groovy configurator, the java nature sets up normally. And of course m2e is upset about the unmapped groovy goals.
Comment 1 benson margulies CLA 2011-05-30 19:01:15 EDT
The problem here is that the groovy configurator pointed to here will add nonexistent source folders, and then eclipse gets more and more unhappy. This is probably not an m2e issue.
Comment 2 Igor Fedorenko CLA 2011-05-30 19:37:15 EDT
Closing as per the last comment. Feel free to reopen if you think m2e could handle this project better, provide better diagnostics, more logs, etc.
Comment 3 Denis Roy CLA 2021-04-19 13:21:55 EDT
Moved to https://github.com/eclipse-m2e/m2e-core/issues/