Community
Participate
Working Groups
Currently a log warning/error is reported if a bundle dependencies on other plugins (or imports) are not not met, but no such warning/error is reported if a plugin's minimum Execution Environment is not met. As a motivating use case: This generated some confusion on some users (and me) on the latest release of the project I work on, which now required Java 7. The plugins failed to load for users inadvertently still running Java 6, but the problem was not clear to diagnose because no feedback at all is provided, not even in the log. The plugins just fail to resolve.
(In reply to Bruno Medeiros from comment #0) > Currently a log warning/error is reported if a bundle dependencies on other > plugins (or imports) are not not met, but no such warning/error is reported > if a plugin's minimum Execution Environment is not met. > Are you referring to errors at development time in PDE, or at runtime? > As a motivating use case: This generated some confusion on some users (and > me) on the latest release of the project I work on, which now required Java > 7. The plugins failed to load for users inadvertently still running Java 6, > but the problem was not clear to diagnose because no feedback at all is > provided, not even in the log. The plugins just fail to resolve. Is this using Kepler 3.9 or one of the latest Luna builds? We did loose some error logging in Luna when bundles cannot resolve. Previously (in Kepler) the launcher would detect unresolved bundles and log a message, but this only happens for two cases: 1) some exception happened trying to launch the eclipse application. 2) if -debug is specified AND new bundles were installed.
(In reply to Thomas Watson from comment #1) > (In reply to Bruno Medeiros from comment #0) > > Currently a log warning/error is reported if a bundle dependencies on other > > plugins (or imports) are not not met, but no such warning/error is reported > > if a plugin's minimum Execution Environment is not met. > > > > Are you referring to errors at development time in PDE, or at runtime? > Runtime. > > Is this using Kepler 3.9 or one of the latest Luna builds? We did loose > some error logging in Luna when bundles cannot resolve. Previously (in > Kepler) the launcher would detect unresolved bundles and log a message, but > this only happens for two cases: > > 1) some exception happened trying to launch the eclipse application. > 2) if -debug is specified AND new bundles were installed. This is using Kepler, not Luna. (Core Runtime is 3.9, if that is the plugin you are looking for)
Can you give us steps to reproduce? How are you launching equinox/eclipse? Are you looking for a development time warning (when running eclipse from your workspace) or a deployment time error when the bundle is installed into a proper installation of eclipse/equinox? I get a log like this when I run on Java 6 with a Java 7 specified execution environment: !ENTRY org.eclipse.osgi 2 0 2013-09-18 10:19:28.002 !MESSAGE The following is a complete list of bundles which are not resolved, see the prior log entry for the root cause if it exists: !SUBENTRY 1 org.eclipse.osgi 2 0 2013-09-18 10:19:28.002 !MESSAGE Bundle test.bug417336_1.0.0.qualifier [1] was not resolved. !SUBENTRY 2 test.bug417336 2 0 2013-09-18 10:19:28.003 !MESSAGE Missing required capability Require-Capability: osgi.ee; filter="(&(osgi.ee=JavaSE)(version=1.7))". But I only get this on the first run. Any runs after that do not log the message again unless I clean the cache and start over. We do this to avoid logging the same resolution errors each launch and filling the log file with the same errors over and over when in development mode. I would also like to know the type of warning messages you get for other missing dependencies, the reason is because the same code should be logging all unresolved dependencies.
(In reply to Thomas Watson from comment #3) > Can you give us steps to reproduce? How are you launching equinox/eclipse? > Are you looking for a development time warning (when running eclipse from > your workspace) or a deployment time error when the bundle is installed into > a proper installation of eclipse/equinox? > I get a development time warning already (both on the PDE validation screen only, and the log itself.). It's on the non-development scenario that I get no warning. A deployment time warning would be ok, but ideally I want a runtime time warning, every time Eclipse is started and the EE constraint is not met. This is because the JVM you run Eclipse with can change after installation, even if it's uncommon for that to happen with a JVM version downgrade. But it could happen, even if by user mistake (some platforms, like MacOS X are trickier to manage the JVMs, so I guess are more prone to these mistakes). In any case, on the non-development scenario I don't get any kind of runtime error, not even deployment. To reproduce, just grab a Kepler platform build (I think previous Eclipse versions have the same issue though), and follow the installation for this IDE: http://code.google.com/p/ddt/wiki/Installation but use a 1.6 JVM instead. The DDT IDE will install successfully, but upon Eclipse restarting, DDT will not be activated. The plugins will not be resolved (they show up in the configuration screen as "[Installed]"), but no log message exists. All I get is some unrelated messages, similar to these: !ENTRY org.eclipse.equinox.p2.repository 2 0 2013-09-19 17:14:41.739 !MESSAGE Server returned lastModified <= 0 for http://updates.ddt.googlecode.com/git/compositeContent.xml > > I would also like to know the type of warning messages you get for other > missing dependencies, the reason is because the same code should be logging > all unresolved dependencies. I'm not sure how to create missing dependencies, outside of the development-time scenario (hosted Eclipse)... I tried to just delete the jar of one of the DDT plugins and start Eclipse. I didn't get any message at all either, strangely enough.
There is a same situation on PyDev. http://www.eclipse.org/forums/index.php/t/652689/ http://stackoverflow.com/questions/19835567/upgraded-to-pydev-3-not-working-with-eclipse-4-3-kepler-on-mac-64-bit-cocoa http://stackoverflow.com/questions/19894995/pydev-perspective-not-showing-after-install-for-eclipse ... It's better to inform users as mismatched environment.
This looks like a dup of bug 378943.
Any updates on this? My users are stumbling with the same issue again now that we are upgrading our IDEs (DDT/Goclipse/RustDT) to use Java 8. I had to resort to creating a workaround plugin (with early startup activation), whose only job is to check the Java version, and show a message dialog to the user if the JVM version is below the requirements.
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.
