Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Pseudo-singleton for Guava in RC3


Guess you know now it's not related to bug 436418, given the discussion and diagnosis given there.

Ordinarily, it's hard to infer much by "what's in the directory and what's not" ... at least, as I understand it ...
the exact point that bundles/features are "cleaned up" after multiple installs is an "implementation detail" of
when p2 does "garbage collection" and, from my memory, is not that predictable.

Unfortunately, I'm not sure "how to tell" what's current .... what's in "bundle info" file or "artifacts xml" ...
perhaps a p2 committer will see this and say.

In any case, in the latest repo report,
it seems we are down to 2 versions in Sim. Release repo: 12 and 15.
I've not looked at log, but am curious who will requires "12" and if that's a hard requirement, an oversight,
or perhaps a mistake in the way constraints are specified?

Hope RC is better ... at least in terms of what gets in EPP packages, if nothing else.

I hope you'll continue your investigations and keep us all posted.


From:        Ed Willink <ed@xxxxxxxxxxxxx>
To:        Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>,
Date:        06/03/2014 02:23 AM
Subject:        [cross-project-issues-dev] Pseudo-singleton for Guava in RC3
Sent by:        cross-project-issues-dev-bounces@xxxxxxxxxxx


I'm not sure if the following is an RC3 regression or an improvement;
it's certainly surprising.

Up until RC2 multiple Guava's could accumulate in the plugins directory.

While incrementally building another RC3 installation from ZIPs to
observe the plugins directory, I saw

Installation of Platform, EMF, GEF
- no
Installation of MWE 2.6.0
- 10.0 (Bug 436420 raised)
Installation of Xtend from M2T/Xpand RC1
- no change
Installation of Xtext 2.6.0
- 10.0 is removed
- 15.0 is added
- 15.0 is added
Installation of Papyrus 1.0.0 RC1
- 15.0 is removed
- 15.0 remains
- 12.0 is added

The removals above are new to RC3 and are perhaps beneficially enforcing
a pseudo-singleton.

Was this really intended? Is it related to:

in which the Plugin registry no longer has dependents.


        Ed Willink
cross-project-issues-dev mailing list

Back to the top