[cross-project-issues-dev] Is it Wednesday yet? RC3 staging repo is complete

[David M Williams]

I must admit, I do still feel confused because none of my neighbors have 
put out their trash, for Thursday morning pick up ... I'm beginning to 
think maybe my neighborhood is in its own little time warp ... a sure sign 
of sleep deprivation?  :) 

http://download.eclipse.org/releases/staging/ 

Much appreciate everyone's efforts! I hope you see the benefits as clearly 
as I do. 

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Missing legal files

[Greg Watson]

Wow man, cosmic :-) It’s working for me too now.

Greg

On Jun 4, 2014, at 3:16 PM, Denis Roy  wrote:

> It works now.  I guess Greg and I had an unusual cosmic connection and we 
> both tried at the same time.
> 
> 
> 
> On 06/04/2014 03:14 PM, Wayne Beaton wrote:
>> Works for me.
>> 
>> Maybe there was a build in progress?
>> 
>> Wayne
>> 
>> On 06/04/2014 03:08 PM, Denis Roy wrote:
>>> Am I the only one getting a 404 on that URL?
>>> 
>>> Denis
>>> 
>>> On 06/04/2014 11:45 AM, Wayne Beaton wrote:
 Some projects are missing required legal files in downloads.
 
 The master list is here:
 
 http://build.eclipse.org/simrel/luna/reporeports/reports/layoutCheck.txt
 
 I've contacted representatives from each project separately. This needs to 
 be addressed.
 
 Thanks for your attention in this matter.
 
 PMC-approved review materials are due today.
 
 Wayne
>>> 
>>> 
>>> 
> 
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Missing legal files

[Denis Roy]

It works now.  I guess Greg and I had an unusual cosmic connection and 
we both tried at the same time.




On 06/04/2014 03:14 PM, Wayne Beaton wrote:

Works for me.

Maybe there was a build in progress?

Wayne

On 06/04/2014 03:08 PM, Denis Roy wrote:

Am I the only one getting a 404 on that URL?

Denis

On 06/04/2014 11:45 AM, Wayne Beaton wrote:

Some projects are missing required legal files in downloads.

The master list is here:

http://build.eclipse.org/simrel/luna/reporeports/reports/layoutCheck.txt

I've contacted representatives from each project separately. This 
needs to be addressed.


Thanks for your attention in this matter.

PMC-approved review materials are due today.

Wayne






___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Missing legal files

[David M Williams]

The reports do "come and go" when new builds are promoted to "staging". 

If you try http://build.eclipse.org/simrel/luna/reporeports/
There should be a polite message saying they are "being generated, check 
back later". 

Apologies for not having a "friendlier" solution implemented yet. 





From:   Denis Roy 
To: cross-project-issues-dev@eclipse.org, 
Date:   06/04/2014 03:08 PM
Subject:Re: [cross-project-issues-dev] Missing legal files
Sent by:cross-project-issues-dev-boun...@eclipse.org



Am I the only one getting a 404 on that URL?

Denis

On 06/04/2014 11:45 AM, Wayne Beaton wrote:
Some projects are missing required legal files in downloads.

The master list is here:

http://build.eclipse.org/simrel/luna/reporeports/reports/layoutCheck.txt

I've contacted representatives from each project separately. This needs to 
be addressed.

Thanks for your attention in this matter.

PMC-approved review materials are due today.

Wayne
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Missing legal files

[Wayne Beaton]

Works for me.

Maybe there was a build in progress?

Wayne

On 06/04/2014 03:08 PM, Denis Roy wrote:

Am I the only one getting a 404 on that URL?

Denis

On 06/04/2014 11:45 AM, Wayne Beaton wrote:

Some projects are missing required legal files in downloads.

The master list is here:

http://build.eclipse.org/simrel/luna/reporeports/reports/layoutCheck.txt

I've contacted representatives from each project separately. This 
needs to be addressed.


Thanks for your attention in this matter.

PMC-approved review materials are due today.

Wayne




___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev


--
Wayne Beaton
Director of Open Source Projects, The Eclipse Foundation 


Learn about Eclipse Projects 
EclipseCon France 2014 
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Missing legal files

[Thanh Ha]

URL works for me.


Thanh

On 04/06/14 03:08 PM, Denis Roy wrote:

Am I the only one getting a 404 on that URL?

Denis

On 06/04/2014 11:45 AM, Wayne Beaton wrote:

Some projects are missing required legal files in downloads.

The master list is here:

http://build.eclipse.org/simrel/luna/reporeports/reports/layoutCheck.txt

I've contacted representatives from each project separately. This 
needs to be addressed.


Thanks for your attention in this matter.

PMC-approved review materials are due today.

Wayne




___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev


___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Missing legal files

[Greg Watson]

Object not found!

The requested URL was not found on this server. If you entered the URL manually 
please check your spelling and try again.

If you think this is a server error, please contact the webmaster.

Error 404

build.eclipse.org
Wed Jun 4 15:07:01 2014
Apache

On Jun 4, 2014, at 11:45 AM, Wayne Beaton  wrote:

> Some projects are missing required legal files in downloads.
> 
> The master list is here:
> 
> http://build.eclipse.org/simrel/luna/reporeports/reports/layoutCheck.txt
> 
> I've contacted representatives from each project separately. This needs to be 
> addressed.
> 
> Thanks for your attention in this matter.
> 
> PMC-approved review materials are due today.
> 
> Wayne
> -- 
> Wayne Beaton
> Director of Open Source Projects, The Eclipse Foundation
> Learn about Eclipse Projects
> 
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Missing legal files

[Denis Roy]

Am I the only one getting a 404 on that URL?

Denis

On 06/04/2014 11:45 AM, Wayne Beaton wrote:

Some projects are missing required legal files in downloads.

The master list is here:

http://build.eclipse.org/simrel/luna/reporeports/reports/layoutCheck.txt

I've contacted representatives from each project separately. This 
needs to be addressed.


Thanks for your attention in this matter.

PMC-approved review materials are due today.

Wayne


___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] Disk usage report for Hudson/Build

[genie]

Compiled 2014-06-04T12:07

 build.eclipse.org 
-> Usage exceeding 1GB for: Hudson master jobs and workspace (2014-06-04T10:00)
  32.9G ep44N-unit-lin64
   4.1G tycho-bpmn2modeler-0.0.1-nightly
   2.7G emf-emfclient-integration
   2.6G papyrus-trunk-nightly-tests
   2.6G gef4-master
   2.3G papyrus-trunk-nightly
   2.1G osee-dev
   1.9G emf-emfclient-maintenance
   1.8G emf-cdo-integration
   1.8G stardust-luna
   1.6G emf-cdo-maintenance
   1.6G emft-featuremodel-editor-xtext
   1.4G amp-integration
   1.4G emf-emfclient-test
   1.4G koneki-ldt-maintenance
   1.4G webtools-vjet-juno
   1.3G emffacet-nightly
   1.2G tycho-gmp.gmf.tooling
   1.2G buckminster-voicetools-targetplatform
   1.1G nattable-snapshot
   1.1G buckminster-egf-helios
   1.1G emf-core-head
   1.1G emf-emfstore-fuzzytests-explorer
   1.1G buckminster-egf-juno
   1.1G mylyn-release
-> Usage exceeding 1GB for: /shared (1000G capacity) (2014-06-04T10:00)
 226.7G technology
 127.0G jobs
  98.9G hipp
  81.4G eclipse
  65.8G rt
  30.0G webtools
  23.1G SLES
  11.0G tools
  10.6G common
   9.2G simrel
   6.7G cbi-ng
   5.3G modeling
   2.3G orbit
   1.6G mylyn
   1.4G soa
   1.3G cbi
-> Usage exceeding 1GB for: /shared/modeling
   3.1G build
-> Usage exceeding 1GB for: /shared/tools
   4.6G tm
   2.4G objectteams
   1.4G mtj
   1.1G aspectj
   1.1G windowbuilder
-> Usage exceeding 1GB for: /shared/technology
 203.2G epp
   9.8G sapphire
   4.8G stem
   3.6G babel
   2.4G cosmos
 END: build.eclipse.org 


 hudson-slave1.eclipse.org 
/dev/xvda1158G   78G   80G  50% /
-> Usage exceeding 1GB for: Hudson workspace on hudson-slave1 (50G capacity) 
(2014-06-03T21:00)
   8.9G mihini-nightly
   4.0G tycho-mat-nightly
   3.1G koneki-ldt
   2.6G koneki-ldt-maintenance
   1.9G cdt-nightly
   1.6G cdt-maint
   1.5G cdt-legacy
   1.3G papyrus-trunk-extra-nightly
   1.2G Xtext-nightly-Maintenance
   1.2G papyrus-trunk-nightly-tests
   1.2G gef-master
   1.2G papyrus-0.10-maintenance-nightly-tests
   1.2G mylyn-integration
   1.1G mylyn-integration-standalone
   1.0G cdt-nightly-3.8
 END: hudson-slave1.eclipse.org 


 hudson-slave2.eclipse.org 
-> Usage exceeding 1GB for: 
 END: hudson-slave2.eclipse.org 


 hudson-slave3.eclipse.org 
/dev/xvda1 55G   33G   23G  59% /
-> Usage exceeding 1GB for: Hudson workspace on hudson-slave3 (50G capacity) 
(2014-06-03T18:00)
   1.0G dltk-nightly
 END: hudson-slave3.eclipse.org 

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] Missing legal files

[Wayne Beaton]

Some projects are missing required legal files in downloads.

The master list is here:

http://build.eclipse.org/simrel/luna/reporeports/reports/layoutCheck.txt

I've contacted representatives from each project separately. This needs 
to be addressed.


Thanks for your attention in this matter.

PMC-approved review materials are due today.

Wayne
--
Wayne Beaton
Director of Open Source Projects, The Eclipse Foundation 


Learn about Eclipse Projects 
EclipseCon France 2014 
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] We will soon be removing old, non-released versions of JDT Compiler in "eclipse-staging"

[David M Williams]

Currently scheduled for Friday, 6/6, Noon, Eastern time. 

Sorry for the short notice, but if anyone would like to review, please see 
bug 436481. 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=436481

But otherwise, be sure to move up to use the "final Luna Release version" 
by then, if you have been using some previous milestone version. 

The "final" Luna version is 3.10.0.v20140603-1928. 
(Say "final" in quotes ... just because there is some rare chance that a 
"blocking problem" will be found and we'll have to produce yet another 
final version.)

I know some projects for Luna may already have fixed all their bugs, say 
in RC1, or RC2, and will be wondering if they should recompile with final 
version. 
Chances are, it would make no difference to your byte codes (unless you 
use Java 8 BREE), since all recent changes were concerned with Java 8 
constructs ... but ... if you wanted to be completely safe, it wouldn't 
hurt to recompile with final version. If you want to check Git history 
yourself, so see if you might be effected, you could study the log at 
http://git.eclipse.org/c/jdt/eclipse.jdt.core.git/log/. 

We do want to "get rid of the old" for two reasons, though ... one is to 
make sure teams do "move up" to final version for their final builds (if 
they are still building, and have been using any of the milestone versions 
of the compiler) and second reason, is we want to make sure the JDT Team 
is not burdened with bogus bugs about a problem with such and such version 
of compiler, when in fact it was not even a released version and may 
already be fixed. 

If anyone has any "special requests" (such as they need a particular 
version left in "staging" for a little longer, for some reason ... maybe 
your releng guy is on vacation till Monday :) ... then please comment in 
bug 436481 with the details. 

And, if not obvious, if anyone sees any issues with the lists and 
tabulations I've put in bug 436481, feel free to comment in that bug. 

Thanks, 
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

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

[Ed Willink]

  
  
Hi David

On 04/06/2014 11:48, David M Williams
  wrote:


> I think that someone with the power to influence the
platform needs
to review how 
  
  > we support Guava and other shared
non-singletons
  
  
  > so that we avoid repeating this mess in Mars.
  
  
  Hmmm, I think, Ed, I finally
found one
thing to disagree with you about :) 
  

Hopefully we're agreed about trying to avoid this mess in Mars. If
tooling rather than the platform is the solution, fine by me.

  
  I think if you (or others)
carefully
read Bug 427862
you'd find this issue less about "using one version" and more
about using correct versions, in correct ways:  a) projects
should
follow "best practices" for componentization (such as, 1) do
not "re-export" bundles simply for a convenience, 2) don't make
"third party" code part of your own API (unless it's one that's
mature, and one that can be well trusted to follow OSGi
principles), 3)
use proper version ranges when exporting or importing packages,
4) take
advantage of "uses clauses", etc.) and b) we need to influence
those third parties who are not using OSGi quite right, and
encourage them
to do so (which has happened, in this case!)
  

Thanks for pointing back at this. I didn't understand "uses" and got
Marcel to give a better example.

I see that the Manifest editor has a "Calculate Uses" button that
makes my Manifests huge. I don't particularly want to maintain this
manually.

I noticed long ago that MANIFEST.MF as shipped by SimRel bears
little resemblance to my source text. There is a nasty line-wrapping
and every class has an SHA1-Digest added.

If something is rewriting all the Import-Package directives, then
surely it could/should rewrite all the Export-Package directives to
use "uses" too?

    Regards

        Ed Willink

  

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

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

[David M Williams]

> I think that someone with the power to influence the platform needs to 
review how 
> we support Guava and other shared non-singletons 
> so that we avoid repeating this mess in Mars.

Hmmm, I think, Ed, I finally found one thing to disagree with you about :) 


I think if you (or others) carefully read Bug 427862 you'd find this issue 
less about "using one version" and more about using correct versions, in 
correct ways:  a) projects should follow "best practices" for 
componentization (such as, 1) do not "re-export" bundles simply for a 
convenience, 2) don't make "third party" code part of your own API (unless 
it's one that's mature, and one that can be well trusted to follow OSGi 
principles), 3) use proper version ranges when exporting or importing 
packages, 4) take advantage of "uses clauses", etc.) and b) we need to 
influence those third parties who are not using OSGi quite right, and 
encourage them to do so (which has happened, in this case!)

It seems all (or many) of those things have happened for Guava, I assume 
partially due to your efforts, so I do not think there is a problem for 
"the platform" to solve ... and think that we all need to learn more about 
correct componentization, following OSGi guidelines and best practices. 
(And, I know, that's not easy  but, do believe that's the best 
solution).  Almost anything that is solved by "having only one version" is 
simply "building one application" ... not "building components". Not to 
mention, this painful experience has shown the importance of the 
"Simultaneous Release Train" ... it would have taken years to sort this 
out, if everyone was on their own, unrelated, schedule. 

In short, I don't think you give yourself enough credit on how much you've 
improved things ... not because we use "one version", but because we use a 
"proper version" in the "the correct way". 

Perhaps I am over simplifying, or not aware of still-lurking problems? Or, 
perhaps you simply mean we need better tools; such as warning people if 
they re-export foreign bundles (or, if they use a bundle that does that 
questionable practice) ...  or don't properly use versions when 
exporting/importing packages (the former, I think might be valid 
enhancement request, the latter I believe is implemented, but defaults to 
"off"?) 

But most of all, I want to say thanks to you, and everyone else who has 
worked hard to get past this particular issue, and am sure we all would 
respect concrete requests to improve tools ... but, naturally, making the 
request is not the same as "getting it done" and I hope everyone knows we 
can't always rely on a "nebulous platform" to solve problems, but ask 
ourselves, "what can I implement". 

Thanks again for your (continued) efforts, 





From:   Ed Willink 
To: Cross project issues , 
Date:   06/04/2014 04:33 AM
Subject:Re: [cross-project-issues-dev] Pseudo-singleton for Guava 
in RC3
Sent by:cross-project-issues-dev-boun...@eclipse.org



Hi

Papyrus is 12, skipped RC2, but I think should be ok for RC3.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=422745
Further to my earlier, 10, then 15 then 12 observations. When I then 
install Mylyn Wikitext, 15 came back again, 12 stayed.

Hopefully a de facto 15-only policy will hide the problems, until users 
add third party non-15 contributions.

I think that someone with the power to influence the platform needs to 
review how we support Guava and other shared non-singletons so that we 
avoid repeating this mess in Mars.

Regards

Ed Willink

On 04/06/2014 01:44, David M Williams wrote:
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  
To:Cross project issues , 
Date:06/03/2014 02:23 AM 
Subject:[cross-project-issues-dev] Pseudo-singleton for Guava in 
RC3 
Sent by:cross-project-iss

Re: [cross-project-issues-dev] DLTK in Luna ?

[Dawid Pakuła]

Hi,

Luna RC3 stagging repo still contain 5.0 (kepler) release.

--
Dawid Pakuła 
+48 795 996 064

From: Alexey Panchenko alex.panche...@gmail.com
Reply: Cross project issues cross-project-issues-dev@eclipse.org
Date: 7 maja 2014 at 19:56:31
To: Cross project issues cross-project-issues-dev@eclipse.org
Subject:  Re: [cross-project-issues-dev] DLTK in Luna ?  

Hi,

The current status is:
- I recently changed version to 5.1 on master
- going to contribute it to Luna ~RC1
- there should not be any compatibility problems

Regards,
Alex


On Wed, May 7, 2014 at 6:14 PM, Simon Bernard  
wrote:
We still got no answer about DLTK integration in Luna.
Currently, in SimRel, DLTK is only at v5.0.0 (Kepler version).
Hoping, we will not face last-minute compatibility problems.
Simon

Le vendredi 18 avril 2014 à 08:46 -0700, Simon Bernard a écrit :
> Hi,
> I have few questions about the next dltk integration in
> Luna :
>  Does an update site exist to test the next version of DLTK (5.1)?
>  Currenlty, there still are the dltk 5.0 version, do you plan to
> integrate a development version of DLTK (5.1) for M7 of Luna ?
> Thx.
> Simon
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

___  
cross-project-issues-dev mailing list  
cross-project-issues-dev@eclipse.org  
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev  
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

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

[Ed Willink]

  
  
Hi

Papyrus is 12, skipped RC2, but I think should be ok for RC3.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=422745
Further to my earlier, 10, then 15 then 12 observations. When I then
install Mylyn Wikitext, 15 came back again, 12 stayed.

Hopefully a de facto 15-only policy will hide the problems, until
users add third party non-15 contributions.

I think that someone with the power to influence the platform needs
to review how we support Guava and other shared non-singletons so
that we avoid repeating this mess in Mars.

    Regards

        Ed Willink

On 04/06/2014 01:44, David M Williams
  wrote:

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

  
  To:      
 Cross project issues
, 
  
  Date:      
 06/03/2014 02:23 AM
  
  Subject:    
   [cross-project-issues-dev]
Pseudo-singleton
for Guava in RC3
  
  Sent by:    
   cross-project-issues-dev-boun...@eclipse.org
  
  
  
  
  
  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@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
  

  
  
  
  
  ___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

  
  
  
  No virus
found in this message.
Checked by AVG - www.avg.com
Version: 2014.0.4592 / Virus Database: 3955/7615 - Release Date:
06/03/14


  

___
cross-project-issues-dev mailing list
cross-project-issues-de

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

[LETAVERNIER Camille]

Hi,


Ø  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?

Papyrus still includes Guava 12. There's no hard requirement, we just tried to 
be as consistent as possible with other versions deployed in earlier milestones 
(Which was Guava 12 until M7 I think), and didn't update yet.

We've moved to Guava 15 now, so RC3 will be OK.

Camille

De : cross-project-issues-dev-boun...@eclipse.org 
[mailto:cross-project-issues-dev-boun...@eclipse.org] De la part de David M 
Williams
Envoyé : mercredi 4 juin 2014 02:44
À : Cross project issues
Objet : Re: [cross-project-issues-dev] Pseudo-singleton for Guava in RC3

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 mailto:e...@willink.me.uk>>
To:Cross project issues 
mailto:cross-project-issues-dev@eclipse.org>>,
Date:06/03/2014 02:23 AM
Subject:[cross-project-issues-dev] Pseudo-singleton for Guava in RC3
Sent by:
cross-project-issues-dev-boun...@eclipse.org




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@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] RC3 staging repo is NOT complete - my apologies

[David M Williams]

What day is it? :( 
I think the aggregation builds just got so quite I assumed it must be 
Wednesday. :)

As has been said ... one more day (well, rest of today, Wednesday 6/4, 
approximately 5:00. 



From:   Markus Knauer 
To: Cross project issues , 
Date:   06/04/2014 03:00 AM
Subject:Re: [cross-project-issues-dev] RC3 staging repo is 
complete
Sent by:cross-project-issues-dev-boun...@eclipse.org



Yep, it's very easy to get confused by so many timezones, build dates, 
etc.
I'm pretty sure there are a couple of hours left for projects to 
contribute to RC3 (+3).

Thanks,
Markus


On Wed, Jun 4, 2014 at 8:29 AM, Matthias Sohn  
wrote:
On Wed, Jun 4, 2014 at 6:07 AM, Eike Stepper  wrote:
Hi David,

Not that I'm affected because CDO is at +2, but what happened to RC3+3?


If you skip RC3+3 JGit and EGit don't get a chance to update for RC3
 

Am 04.06.2014 02:51, schrieb David M Williams:
*http://download.eclipse.org/releases/staging/*

*Test well, questions (or issues) welcome. *

*You know the drill ... if no blockers found ... will become visible at 
.../releases/luna on Friday. *

*As an early reminder, once we produce RC4, it will not be promoted to 
.../releases/luna until the official release day
(Jun 25) since otherwise in effect we'd be "releasing early". *

*Thanks for everyone's continued contributions -- hang in there! *



___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev


___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev


___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev


___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] RC3 staging repo is complete

[Markus Knauer]

Yep, it's very easy to get confused by so many timezones, build dates, etc.
I'm pretty sure there are a couple of hours left for projects to contribute
to RC3 (+3).

Thanks,
Markus


On Wed, Jun 4, 2014 at 8:29 AM, Matthias Sohn 
wrote:

> On Wed, Jun 4, 2014 at 6:07 AM, Eike Stepper  wrote:
>
>> Hi David,
>>
>> Not that I'm affected because CDO is at +2, but what happened to RC3+3?
>>
>
>
> If you skip RC3+3 JGit and EGit don't get a chance to update for RC3
>
>
>>
>> Am 04.06.2014 02:51, schrieb David M Williams:
>>
>>> *http://download.eclipse.org/releases/staging/*
>>>
>>> *Test well, questions (or issues) welcome. *
>>>
>>> *You know the drill ... if no blockers found ... will become visible at
>>> .../releases/luna on Friday. *
>>>
>>> *As an early reminder, once we produce RC4, it will not be promoted to
>>> .../releases/luna until the official release day
>>> (Jun 25) since otherwise in effect we'd be "releasing early". *
>>>
>>> *Thanks for everyone's continued contributions -- hang in there! *
>>>
>>>
>>>
>>> ___
>>> cross-project-issues-dev mailing list
>>> cross-project-issues-dev@eclipse.org
>>> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>>>
>>>
>> ___
>> cross-project-issues-dev mailing list
>> cross-project-issues-dev@eclipse.org
>> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>>
>
>
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
>
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev