|
| Re: P2 Director fails during startup due to a conflicting (JVM?) dependency [message #1716929 is a reply to message #1716883] |
Wed, 09 December 2015 06:11  |
 Ed Merks
Messages: 33258
Registered: July 2009 |
Senior Member |
|
|
Commands below.
On 08/12/2015 9:37 PM, J A Morton wrote:
> Problem may be related to thread starting with message 1441934 on 2014-10-10, entitled "Cannot complete the install because of a conflicting dependency. on Mars (Latest)". The good news is that the problem does not seem to affect any other part of Eclipse Mars. (Side Issue : not happy about the surprise inclusion of OOMPH 1.3.0.v20150923-1022 - let me chose if I want it!).
Is it the version your not happy about?
>
>
> BACKGROUND:
>
> Platform is 32 bit Win 7 Enterprise SP1, running as regular user (i.e. on an IM controlled machine, I don't have Admin rights). OOMPH is version 1.3.0.v20150923-1022 on Mars 4.5.1 20150924-1200. Java 1.7 (portable version) & 1.8.0_60 is installed (both are standard VMs) in Mars - which is set up to use 1.7.
>
> Downloaded the standard Mars package from eclipse.org and installed it in a different folder than used by my previous version (Kepler). Excluding OOMPH, everything in the standard package installed properly as did the additional packages I was using with Kepler, i.e. Pydev (Python 3.2.2) and IBM/Rational's Jazz packages.
So for so good.
>
> THE PROBLEM:
>
> Here's the error (see the "OOMPH 'failed tasks' - details.txt" attachment) that I get when I click on the flashing icon that appears at startup in the bottom right of the Eclipse window :
> -----
> Updating locks...
> Calculating requirements and dependencies.
> Cannot complete the request. Generating details.
> ERROR: org.eclipse.equinox.p2.director code=10054 Cannot complete the install because of a conflicting dependency.
> at org.eclipse.oomph.util.OomphPlugin.coreException(OomphPlugin.java:280)
> at org.eclipse.oomph.p2.internal.core.ProfileTransactionImpl.resolve(ProfileTransactionImpl.java:413)
> >>> omitting 11 levels of traceback <<<
> at org.eclipse.oomph.setup.ui.wizards.ProgressPage$9.run(ProgressPage.java:552)
> at org.eclipse.oomph.setup.ui.wizards.ProgressPage$11$1.run(ProgressPage.java:671)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> ERROR: org.eclipse.equinox.p2.director code=0 Software being installed: artificial_root 1.0.0.v1449584701164
> ERROR: org.eclipse.equinox.p2.director code=1 Only one of the following can be installed at once:
> ERROR: org.eclipse.equinox.p2.director code=0 Java Development Tools Core 3.11.1.v20150902-1521 (org.eclipse.jdt.core 3.11.1.v20150902-1521)
> ERROR: org.eclipse.equinox.p2.director code=0 Object Teams Development Tooling Core 3.11.1.v_OTDT_r241_201509081206 (org.eclipse.jdt.core
> 3.11.1.v_OTDT_r241_201509081206)
> ERROR: org.eclipse.equinox.p2.director code=0 Java Development Tools Core 3.6.51.v_B83_R36x_J7 (org.eclipse.jdt.core 3.6.51.v_B83_R36x_J7)
>
> -----
>
> QUESTION : How do I eliminate the conflict?
This problem relates to the recently opened
https://bugs.eclipse.org/bugs/show_bug.cgi?id=483868. Firstly, one
simple way to avoid this issue to disable Window -> Preferences -> Oomph
-> Setup Tasks -> Skip automatic task execution on startup. Then the p2
director task won't perform and you won't be affected as you continue to
use your installation.
Please add your findings to that bugzilla. I think two issues need
consideration. One is the test for the p2 director task's is needed.
It currently checks, on startup trigger, if the things that are required
to be installed are installed, but it also checks if they are within the
version range of the requirements; I'm not sure if that's a good idea
because it will automatically try to do an update. In any case, the
primary problem of this bug seems to be that the combination of the
requirements created for what's currently installed (which might have
been installed not using Oomph) along with the requirements from the p2
task itself can be inherently conflicting. In this case it might be
more related to whether some type of remediation is being applied
because it is clear you can't have both JDT 3.6 and 3.11 installed,
though it's not clear what specifically is requiring JDT 3.6. Perhaps
bad logic in the p2 directory task when synthesizing the profile change
request.
In the ideal world you would describe repeatable steps we could use the
reproduce this problem. I'm not sure we can install Rational Team
Concert when testing...
>
> The attached background files are:
>
> 1 - OOMPH 'failed tasks' window.png : the OOMPH "Progress" window (pops up when you click on the flashing icon at the bottom right of the eclipse window) that lists the P2 Director "failed tasks";
> 2 - OOMPH 'failed tasks' - details.txt" : contains the details in the bottom of the above attachment (my comments are wrapped in >>> <<<);
> 3 - Mars - installation details.png" : shows the software installed into Mars (note that the the "Plug-ins" tab was empty);
> 4 - Mars - session log.txt" : status log for the latest Eclipse session showing the problems (keybinding errors & P2 Director problem)
>
>
>
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
Powered by
FUDForum. Page generated in 0.02975 seconds
] 
Search
Help
Register
Login
Home
