Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 93454 - Non default source folders in a plugin
Summary: Non default source folders in a plugin
Status: RESOLVED DUPLICATE of bug 34165
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: PDE-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-05-02 16:47 EDT by Marshall Culpepper CLA
Modified: 2005-06-15 21:41 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marshall Culpepper CLA 2005-05-02 16:47:43 EDT
My plugin projects all have their main source directory set to "src/main". If I
use PDE Tools > Update Classpath to update the dependencies on other plugins,
the source directory is reset to "src"
Comment 1 Wassim Melhem CLA 2005-05-02 16:51:40 EDT
Make sure your build.properties references src/main, not src.  
The mapping of the jar to the source folder supercedes any nesting of folders.

is that the case here?
Comment 2 Marshall Culpepper CLA 2005-05-02 16:56:06 EDT
Ah, yes it is =).

Is it possible to have PDE automatically update the build.properties with the
list of source directories from the project? We could avoid this duplication of
effort in the future...
Comment 3 Wassim Melhem CLA 2005-05-02 17:48:22 EDT
the thing is that your plugin can have more than one library and multiple 
source folders (some of which may not map to any library).  So we can never 
guess what you want to do.

What we could do is flag a warning on your build.properties file if it 
references a non-existing source folder, since that is the big problem.
Comment 4 Wassim Melhem CLA 2005-06-15 21:41:17 EDT
This extra build.properties validation will be addressed as part of bug 34165

*** This bug has been marked as a duplicate of 34165 ***