Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 75765 - jar names should be checked
Summary: jar names should be checked
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 enhancement (vote)
Target Milestone: ---   Edit
Assignee: PDE-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-10-07 00:22 EDT by Jeff McAffer CLA
Modified: 2004-10-26 04:05 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 Jeff McAffer CLA 2004-10-07 00:22:13 EDT
3.1m2

the name of the code jar for a plugin appears in two places, the 
plugin.xml/manifest.mf and the build.properties.  It would be good if there was 
a warning if the value in the manifest.mf does not have an entry in the 
build.properties.  

There will be cases where the jar is prebuilt so the build.propreties does not 
have a 
   source.foo.jar=
line.  In this case there are to possibilities.  Either is an over eager 
warning or PDE could be even more deluxe and check the expressions on the 
bin.includes line.  Typically it either has the jar name (third copy) or *.jar.

I just spent about 30 min trying to figure out why it worked fine when running 
self hosted but not when built and deployed (I got class not found exceptions 
everywhere so spent most of my time looking at plugin dependencies, resolved 
states, ...)
Comment 1 Wassim Melhem CLA 2004-10-26 04:05:53 EDT

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