Community
Participate
Working Groups
Build Identifier: 3.7 When you have 2 projects, and one is a plugin dependency to another. There should be a good idea that the IDE update MANIFEST.MF files in both projects accordingly. Reproducible: Always Steps to Reproduce: 1.Create a project ( plugin project type ) and add libraries , for example hibernate. 2.Create another project (plugin project ), and add first project as a plugin dependency. 3.create file hibernate.cfg.xml in root of project, then when the app (runnning withing Eclipse ClassLoader) try to open the config file, it fail.
Eclipse does update files that it knows about, but this hibernate.cfg.xml file isn't something which is a part of Eclipse. If you have an extra feature installed in your IDE then it should take care of updating its configuration files. Moving to PDE/UI for consideration in case I've mis-interpreted your request.
(In reply to comment #1) > Eclipse does update files that it knows about, but this hibernate.cfg.xml file > isn't something which is a part of Eclipse. If you have an extra feature > installed in your IDE then it should take care of updating its configuration > files. > > Moving to PDE/UI for consideration in case I've mis-interpreted your request. Hi DJ, no, the hibernate.cfg.xml is an example. The problem is in MANIFEST.MF of the "core" applicaction, when you add al Plugin Dependency. Maybe, the procedure should check if the plugin dependency has Eclipse-BuddyPolicy=registered, and the add Eclipse-RegisterBuddy=<plugin added maunally> to the main MANIFEST.MF. Regards
This is pretty much asking for the same thing as bug 283495. Marking this as a dupe. There are no plans to add support in PDE for those headers, but as always, patches are welcome. *** This bug has been marked as a duplicate of bug 283495 ***
