Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 108198 - PDE should flag build.properties related problems
Summary: PDE should flag build.properties related problems
Status: RESOLVED DUPLICATE of bug 34165
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: PDE-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-27 13:14 EDT by Ryan Manwiller CLA
Modified: 2005-08-27 19:43 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 Ryan Manwiller CLA 2005-08-27 13:14:01 EDT 
If the plugin has a build.properties, pde should have warnings if
build.properties does not "match" the plugin.

Examples:

The plugin has a source directory that is not listed in build.properties. Bad
result: your built plugin will not contain all the classes you though it would.
Leads to class not found problems.

The plugin.xml or MANIFEST.MF specifies a jar name (library name attribute or
Bundle-ClassPath) that does not match what is in build.properties. Bad result:
plugins depending on your plugin will have class not found problems.

There are probably other build.properties validations that make sense.

These problems should be preferenced so they appear as Error, Warning, (or are
ignored) like the java compiler settings allow. However, the default should be
warning.
Comment 1 Wassim Melhem CLA 2005-08-27 19:43:38 EDT 
will be addressed as part of bug 34165

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