Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 340044 - 0.12 fails to set up java nature on imports
Summary: 0.12 fails to set up java nature on imports
Status: RESOLVED FIXED
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-03-15 11:44 EDT by benson margulies CLA
Modified: 2021-04-19 13:25 EDT (History)
0 users

See Also:


Attachments
Tar file containing project that doesn't work. (1005.50 KB, application/octet-stream)
2011-03-15 11:45 EDT, benson margulies CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description benson margulies CLA 2011-03-15 11:44:57 EDT
Build Identifier: 20100917-0705

I will attach a tarball of a project that, when imported with 0.12 into eclipse, produces a project with no java nature and thus no build path.

Reproducible: Always

Steps to Reproduce:
1. Install the basis-parent pom into your local repo.
2. Import from the site-compiler level.
3. Observe the non-java nature of the resulting projects.
Comment 1 benson margulies CLA 2011-03-15 11:45:49 EDT
Created attachment 191221 [details]
Tar file containing project that doesn't work.
Comment 2 benson margulies CLA 2011-03-15 11:47:34 EDT
This was pilot error. I forgot to change 'pom' to 'jar'.
Comment 3 Denis Roy CLA 2021-04-19 13:25:45 EDT
Moved to https://github.com/eclipse-m2e/m2e-core/issues/