]
Mickael Istria commented on JBIDE-17496:
----------------------------------------
I can easily reproduce it in the "vanilla" configuration. However, I didn't
succeed to reproduce it while debugging.
My first impression is that manipulation of repositories in p2 isn't thread safe. So
that clicking install while Central is still polling repositories to find out what is
up-to-date and what is not seems to cause a conflict and corrupt p2 metadata. If it is so,
then it's not an easy one to fix!
Central installation fails if done right after Eclipse start
------------------------------------------------------------
Key: JBIDE-17496
URL:
https://issues.jboss.org/browse/JBIDE-17496
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: central
Affects Versions: 4.2.0.Beta2
Environment: JBDS 8.0.0.Beta2a B106
Reporter: Martin Malina
Assignee: Mickael Istria
Priority: Critical
Labels: respin-b
Fix For: 4.2.0.Beta2
Attachments: connector-error.png, problems-occurred.png
When you try to install something from Central as soon as JBDS starts for the first time,
you can get errors.
I can reproduce some sort of errors every time (I tried 4 or 5 times), but only on a
completely fresh install of JBDS/JBT (no central repo data cached).
It looks like there is a race condition.
Several times when I tried to install Findbugs, I got:
{quote}
The following connectors are not available: FindBugs
Proceed with the installation anyways?
{quote}
Followed by the Computing connector errors with NPEs familiar from JBIDE-17471
!connector-error.png!
If I proceed anyway, the install dialog is empty.
If I click that I don't want to install, I get this:
{code}
Problems occurred while performing installation: The following connectors are not
available: FindBugs (id=edu.umd.cs.findbugs.plugin.eclipse.feature.group,
site=https://devstudio.jboss.com/updates/8.0-staging/central/core/)
The following connectors are not available: FindBugs
(id=edu.umd.cs.findbugs.plugin.eclipse.feature.group,
site=https://devstudio.jboss.com/updates/8.0-staging/central/core/)
{code}
!problems-occurred.png!