Community
Participate
Working Groups
See https://bugs.eclipse.org/bugs/show_bug.cgi?id=467028#c27 and https://bugs.eclipse.org/bugs/show_bug.cgi?id=467028#c26 for detailed explanation and screenshot of the issue.
An additional comment here is that you have to check the checkbox labelled "Validate Plug-ins automatically prior to launching" to see this prior to launch. Otherwise you have to validate automatically.
(In reply to Sopot Cela from comment #1) > Otherwise you have to validate automatically. I meant manually not automatically.
(In reply to Sopot Cela from comment #1) > An additional comment here is that you have to check the checkbox labelled > "Validate Plug-ins automatically prior to launching" to see this prior to > launch. Filed bug 512528 for the incomplete hack from bug 272076. Steps in I20170220-2000: - import bundles/org.eclipse.equinox.registry from master of git://git.eclipse.org/gitroot/equinox/rt.equinox.bundles.git - fix API baseline (set to 4.6.2) => API Tools reports an "Unknown Resolution Problem": API analysis aborted: org.eclipse.equinox.registry has unresolved constraints: javax.xml.parsers 0.0.0, org.xml.sax 0.0.0, org.xml.sax.helpers 0.0.0 - launch validation reports the same problems The problems are legitimate. CDC-1.1/Foundation-1.1 doesn't include the mentioned packages, so after bug 467028, these imports are indeed unresolvable. Moving this bug to Equinox. The easiest fix is to reduce the BREE to Bundle-RequiredExecutionEnvironment: J2SE-1.4
(In reply to Markus Keller from comment #3) > Moving this bug to Equinox. > > The easiest fix is to reduce the BREE to > Bundle-RequiredExecutionEnvironment: J2SE-1.4 Thanks, I agree with this and will make the update. At some point I think the registry should be updated to something more recent for the BREE, even to Java 8. But I will not do that for this issue.
New Gerrit change created: https://git.eclipse.org/r/91615
Gerrit change https://git.eclipse.org/r/91615 was merged to [master]. Commit: http://git.eclipse.org/c/equinox/rt.equinox.bundles.git/commit/?id=19b35a118a3ed727f414ba14c23412b403eb6daa
(In reply to Markus Keller from comment #3) > The problems are legitimate. CDC-1.1/Foundation-1.1 doesn't include the > mentioned packages, so after bug 467028, these imports are indeed > unresolvable. Something is still wrong with this validation. The context that PDE should be resolving the set of bundles should be the VM that it is going to launch with. That VM is going to contain the javax.xml packages (unless you are running on something less than Java 1.4). The registry bundle imports the javax.xml packages, it should not care if that comes from a bundle or the VM for validation purposes. I don't see the value of forcing a javax.xml bundle in this case where the BREE may specify an EE that does not have the package, but you are launching with one that does have the package. (In reply to Eclipse Genie from comment #6) > Gerrit change https://git.eclipse.org/r/91615 was merged to [master]. > Commit: > http://git.eclipse.org/c/equinox/rt.equinox.bundles.git/commit/ > ?id=19b35a118a3ed727f414ba14c23412b403eb6daa Regardless of the issue in PDE, I did update the registry to remove the Foundation-1.1 support. Moving back to PDE for discussion or closure.
(In reply to Thomas Watson from comment #7) > Something is still wrong with this validation. The context that PDE should > be resolving the set of bundles should be the VM that it is going to launch > with. Good point. Pre-launch validation should use the actual VM. API Tools can't know the actual VM, so the API Tools problem is OK.
*** Bug 512599 has been marked as a duplicate of this bug. ***
Is there any update on this issue or time-frame for resolution? Thanks
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
