Community
Participate
Working Groups
Having stepped up to Eclipse 4.11 it appears that the Manifest Editor does not recognize all Java packages. When I turn to the "Runtime" page of the Manifest Editor and attempt to add a Java package to the Exported Packages list the resulting dialog DOES NOT include my Java package "com.sas.dt.internal.app.common.nls". ONLY when I check the "Show non-Java packages" does my Java package get included in the dialog's list of packages to export. I shall attach a screen shot that shows: - That the package is indeed a Java package. - That the dialog does not include the Java package. - That when I check "Show non-Java packages" the Java package is shown.
Created attachment 277950 [details] Screenshot
Looking at your picture and also at bug 545604 I wonder if you have autobuild turned off or if your workspace is somehow out-of-sync with the file system, or your platform itself contains the bundles you have in the workspace but with different content?
Thanks Andrey... - Auto build is ON. - The workspace is not out-of-sync with the file system. - I am not using a custom PDE platform/target. I am using Eclipse to build a pure OSGi-based application, not a collection of Eclipse plug-ins. While I understand that an Eclipse plug-in IS an OSGi bundle, the opposite is not always true. Background: I'm *very* experienced with using Eclipse's PDE for building plug-in projects, regardless of whether they're Eclipse IDE/RCP plug-ins, or OSGi bundles, having used Eclipse since before version 1.0, and OSGi since its initial specification release. The codebase I'm working on has existed for over 5 years, and is very well tested and understood. So the likelihood is that I'm highlighting genuine bugs in Eclipse PDE. Thanks!
>. I'm highlighting genuine bugs in Eclipse PDE. Looks like a bug in PDE. I tried on few sample projects and it works fine. The only time a package is not seen there is when it has only .properties file or something like that. Once a java file is present, this should not happen at all. Would it be possible for you to create this issue by attaching a sample project where this bug is exhibited?
I can certainly try. Thanks.
I have successfully reproduced the bug! The bug is that when you have a Java package named the same as a non-Java package in another source folder, such as under "resources" (which is very common for storing bundle resources such as externalized strings), the Export Package dialog incorrectly filters out the package. - I shall attach a screen shot. - I shall attach a zip containing a sample project.
Created attachment 277966 [details] Screenshot showing how to reproduce the bug.
Created attachment 277967 [details] Sample project that demonstrates the bug.
Created attachment 277968 [details] Tentative fix
Thanks Vikas for addressing this issue.
(In reply to Vikas Chandra from comment #9) > Created attachment 277968 [details] [diff] > Tentative fix Please use Gerrit as usual.
New Gerrit change created: https://git.eclipse.org/r/139394
Gerrit change https://git.eclipse.org/r/139394 was merged to [master]. Commit: http://git.eclipse.org/c/pde/eclipse.pde.ui.git/commit/?id=62832322e9c431e5c46f4fa6f477b9b4a3d2e9f9
verified in Version: 2019-06 (4.12) Build id: I20190406-1800
