Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 269685 - Importing plug-ins as source should not import .class files
Summary: Importing plug-ins as source should not import .class files
Status: RESOLVED FIXED
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.5   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.5 M7   Edit
Assignee: Ankur Sharma CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-23 09:26 EDT by Markus Keller CLA
Modified: 2009-04-20 10:48 EDT (History)
4 users (show)

See Also:
curtis.windatt.public: review+

Attachments
Patch (4.93 KB, patch)
2009-04-18 14:24 EDT, Ankur Sharma CLA 		curtis.windatt.public: iplog+
Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Markus Keller CLA 2009-03-23 09:26:59 EDT 
I20090317-1745

Importing plug-ins as source should not import .class files. Currently, all class files from the binary plug-in end up in the root of the imported plug-in (in their folders, so you usually just see an 'org' or 'com' folder inside the project).
Comment 1 Curtis Windatt CLA 2009-03-23 14:35:36 EDT 
We do grab files from the binary plug-in in case they are needed for development, but it is supposed to ignore class files.
Comment 2 Ankur Sharma CLA 2009-04-18 14:24:01 EDT 
Created attachment 132336 [details]
Patch

While importing with source, instead of extracting all of it, it now picks non-class files.
Comment 3 Curtis Windatt CLA 2009-04-20 10:48:22 EDT 
Applied patch to HEAD.  Thanks Ankur.