Re: [cross-project-issues-dev] Pseudo-singleton for Guava in RC3

[David M Williams <david_williams@xxxxxxxxxx>]

Ed, 

Guess you know now it's not related
to bug 436418, given the discussion and diagnosis given there. 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=436418

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,

http://build.eclipse.org/simrel/luna/reporeports/reports/nonUniqueVersions.txt
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. 

Thanks, 






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

---

Hi

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 com.google.guava
Installation of MWE 2.6.0
- com.google.guava 10.0 (Bug 436420 raised)
Installation of Xtend from M2T/Xpand RC1
- no change
Installation of Xtext 2.6.0
- com.google.guava 10.0 is removed
- com.google.guava 15.0 is added
- com.google.guava.source 15.0 is added
....
Installation of Papyrus 1.0.0 RC1
- com.google.guava 15.0 is removed
- com.google.guava.source 15.0 remains
- com.google.guava 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:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=436418

in which the Plugin registry no longer has dependents.

     Regards

         Ed Willink
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev