Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 87275 - Listen to library addition
Summary: Listen to library addition
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-03-07 10:52 EST by Pascal Rapicault CLA
Modified: 2005-05-26 01:30 EDT (History)
1 user (show)

See Also:

Attachments
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 Pascal Rapicault CLA 2005-03-07 10:52:58 EST 
When developing plug-ins, two mistakes arise from the fact that the user can 
manually change the java build path: runtime errors (NoClassDefFound 
exceptions) and compile errors when exporting.
I suggest that PDE listens to the java model, and more precisely to the flags: 
F_CLASSPATH_CHANGED, F_ADDED_TO_CLASSPATH, F_CLASSPATH_REORDER.

CC'ing Jerome who gave me the info about the flags
Comment 1 Jerome Lanneluc CLA 2005-03-07 11:05:47 EST 
Another way to prevent the user from messing with the build path (when inside a
PDE project) would be to remove the Java Build Path wizard and the 'Build Path'
context menu.
Comment 2 Jerome Lanneluc CLA 2005-03-07 11:06:56 EST 
The rational is: when using a PDE project, only the plugin.xml should be used to
change the build path
Comment 3 Wassim Melhem CLA 2005-05-26 01:30:37 EDT 
best addressed as part of the bigger build.properties validation item.

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