Re: [cross-project-issues-dev] Luna RC3 repository is available

2014-06-06 Thread David M Williams 
I think they were just waiting for the +1 from the package maintainer, on 
epp-dev list (which was, just given in past few hours) ... so should 
appear soon (well, when ever ?webmaster? is next working and "enables" its 
visibility. 

For future reference, the epp-dev list might be slightly better list for 
such questions ... but this list is ok too. 

Hope that helps, 




From:   Kaloyan Raev 
To: Cross project issues , 
Date:   06/06/2014 04:53 PM
Subject:Re: [cross-project-issues-dev] Luna RC3 repository is 
available
Sent by:cross-project-issues-dev-boun...@eclipse.org



I don't see the PHP package at

http://www.eclipse.org/downloads/index-developer.php

I remember it was there as RC2 package. 

The direct download links work correctly, e.g.

https://www.eclipse.org/downloads/download.php?file=/technology/epp/downloads/release/luna/RC3/eclipse-php-luna-RC3-linux-gtk-x86_64.tar.gz

It is just not available on the download page. Any idea what went wrong?


On Fri, Jun 6, 2014 at 4:03 PM, David M Williams <
david_willi...@us.ibm.com> wrote:
I've made the "RC3" repository visible under the build-in repository at 

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

The EPP packages will be available soon, if not already, from 

http://www.eclipse.org/downloads/index-developer.php 

Happy testing! 


___
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] Slight delay in declaring Eclipse Project's RC4 +0 delivery

2014-06-06 Thread David M Williams 
Our candidate for RC4 is 
http://download.eclipse.org/eclipse/downloads/drops4/I20140606-1215/

And initially we thought the unit tests would be done by now, and we'd 
declare late on our +0 day. But turned out the test job on windows bombed 
out at the beginning (unrelated to our build ... couldn't clean workspace? 
Connection refused? ... ) so I have just now restarted them, and they take 
around 7 or 9 hours to complete. 

While we are 99% sure that I20140606-1215 contains our "final bits" it 
just doesn't seem right to declare the final build of the whole Luna cycle 
without all the unit tests complete ... so ... we'll wait until Saturday 
morning to declare ... assuming the Windows machine can be made to work :) 
... and assuming there's not a lot of unusual failures on Windows (there 
were no failures on the other two platforms ... so ... seems near certain 
the build is the quality we expected ... the delay in making it official 
is simply "procedural". 

In fact, I've gone ahead and submitted the I20140606-1215 to the 
aggregation build, and will promote to staging tonight. So once the CDT 
package is rebuilt and available (Saturday morning? ... from EPP's build 
site, not downloads) ... the bug that gave rise to this last minute respin 
(bug 436758) could be verified fixed, if the originator has the 
opportunity over the weekend. 

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] Luna RC3 repository is available

2014-06-06 Thread Kaloyan Raev 
I don't see the PHP package at

http://www.eclipse.org/downloads/index-developer.php

I remember it was there as RC2 package.

The direct download links work correctly, e.g.

https://www.eclipse.org/downloads/download.php?file=/technology/epp/downloads/release/luna/RC3/eclipse-php-luna-RC3-linux-gtk-x86_64.tar.gz

It is just not available on the download page. Any idea what went wrong?


On Fri, Jun 6, 2014 at 4:03 PM, David M Williams 
wrote:

> I've made the "RC3" repository visible under the build-in repository at
>
> http://download.eclipse.org/releases/luna/
>
> The EPP packages will be available soon, if not already, from
>
> http://www.eclipse.org/downloads/index-developer.php
>
> Happy testing!
>
>
> ___
> 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

2014-06-06 Thread David M Williams 
I'm not sure you ever got answers to some of your questions ... so, just 
in case you still need them  

> 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.

The "wrapping" is part of the "spec" for MANIFEST.MF files and any build 
and any runtime version should be wrapped that way (that is, not exceed 80 
characters ... how old is that! :) 

The SHA Digest is part of the "code signing" that occurs ... again, any 
build that "signs" would have these. 

So, these first two aren't specific to Eclipse, OSGI, or Sim. Release, or 
anything other than "Java". 

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

There are actually some "build tools" that will do that, such as BND ... I 
think its called ...  and not sure if by default, or if you have to spell 
it out ... BUT, we discussed this in Orbit (at least in Orbit, other 
projects may have also) and decided against a blanket "always use 
uses-clauses" because there was some concern that if it was ALWAYS used, 
then it would start to have a performance impact ... not so much for 
"small apps" of several hundred bundles ... but, for cases where several 
thousand bundles were being used, it might start to add up, especially to 
start-up time, and especially to "first time" start-up time. That was many 
many years ago, so not sure if there has been any studies or improvements 
in that concern. But, it is also clear that in some cases, it is 
definitely required, to get components to "play nice" with each other. I'm 
sorry I don't know of a clear statement of "how to know" when its 
required, and when its not ... but if there is one, I bet a search engine 
would find it. (including some interesting, old, bug reports :) 

HTH





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



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

___
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] Switch from Luna RC2 to RC3 fails all our Tycho run UI tests: Known issue?

2014-06-06 Thread Andreas Sewe 
Hi Thomas, hi Igor,

> This is tracked as Tycho
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=436159
> 
> Either use Platform build with 435888 fixed or switch to Tycho
> 0.21 snapshot, which should be more tolerate to exceptions during test
> framework shutdown.

thanks for the prompt reply. Really appreciate it. :-)

Look indeed like Bug 435888. Our build used
org.eclipse.e4.ui.workbench.swt 0.12.100.v20140521-1818 from
<. Now switched to
, which I
probably should have done all along. That seems to have fixed the issue.

Best wishes,

Andreas

-- 
Codetrails UG (haftungsbeschränkt)
The knowledge transfer company

Robert-Bosch-Str. 7, 64293 Darmstadt
Mobile: +49-170-811-3791
http://www.codetrails.com/

Managing Director: Dr. Marcel Bruch
Handelsregister: Darmstadt HRB 91940
___
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] Switch from Luna RC2 to RC3 fails all our Tycho run UI tests: Known issue?

2014-06-06 Thread Igor Fedorenko 

This is tracked as Tycho
https://bugs.eclipse.org/bugs/show_bug.cgi?id=436159

Either use Platform build with 435888 fixed or switch to Tycho
0.21 snapshot, which should be more tolerate to exceptions during test
framework shutdown.

--
Regards,
Igor

On 2014-06-06, 12:17, Thomas Watson wrote:

That looks to be https://bugs.eclipse.org/bugs/show_bug.cgi?id=435888

Tom



Inactive hide details for Andreas Sewe ---06/06/2014 11:13:52 AM---Hi,
hope cross-project-issues is the right list for this, buAndreas Sewe
---06/06/2014 11:13:52 AM---Hi, hope cross-project-issues is the right
list for this, but for us it's a

From: Andreas Sewe 
To: cross-project-issues-dev@eclipse.org
Date: 06/06/2014 11:13 AM
Subject: [cross-project-issues-dev] Switch from Luna RC2 to RC3 fails
all our Tycho run UI tests: Known issue?
Sent by: cross-project-issues-dev-boun...@eclipse.org





Hi,

hope cross-project-issues is the right list for this, but for us it's a
huge issue (none of our builds pass) and I am wondering whether any
other project has encountered this as well:

We use  as update site in
our builds. Now, as of today, i.e., the promotion of RC3 from staging to
said update site, Tycho fails to execute all of our UI tests. I have
opened Bug 436858 [1] to document my findings so far, but the short
version is that the UI tests all fail with the tycho-surefire-plugin
saying some along the lines of

 > An error has occurred. See the log file
.../target/work/data/.metadata/.log.

with the log then containing

 > !ENTRY org.eclipse.osgi 4 0 2014-06-06 09:17:04.074
 > !MESSAGE Application error
 > !STACK 1
 > java.lang.NullPointerException
 > at
org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$StylingPreferencesHandler.getPreferences(PartRenderingEngine.java:1500)
 > at
org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$StylingPreferencesHandler.resetOverriddenPreferences(PartRenderingEngine.java:1470)
 > at
org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$StylingPreferencesHandler$1.handleEvent(PartRenderingEngine.java:1458)
 > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
 > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4487)
 > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4480)
 > at org.eclipse.swt.widgets.Display.release(Display.java:3488)
 > at org.eclipse.swt.graphics.Device.dispose(Device.java:249)
 > at
org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:151)
 > at
org.eclipse.tycho.surefire.osgibooter.UITestApplication.runApplication(UITestApplication.java:31)
 > at
org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.run(AbstractUITestApplication.java:114)
 > at
org.eclipse.tycho.surefire.osgibooter.UITestApplication.start(UITestApplication.java:37)
 > at
org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
 > at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
 > at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
 > at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:382)
 > at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:236)
 > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 > at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
 > at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 > at java.lang.reflect.Method.invoke(Method.java:606)
 > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
 > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
 > at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
 > at org.eclipse.equinox.launcher.Main.main(Main.java:1438)

and possibly a complaint about an invalid thread access (SWTException).

Has anyone else seen this?

Best wishes,

Andreas

[1] 

--
Codetrails UG (haftungsbeschränkt)
The knowledge transfer company

Robert-Bosch-Str. 7, 64293 Darmstadt
Mobile: +49-170-811-3791
http://www.codetrails.com/

Managing Director: Dr. Marcel Bruch
Handelsregister: Darmstadt HRB 91940
___
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] Switch from Luna RC2 to RC3 fails all our Tycho run UI tests: Known issue?

2014-06-06 Thread Thomas Watson 

That looks to be https://bugs.eclipse.org/bugs/show_bug.cgi?id=435888

Tom





From:   Andreas Sewe 
To: cross-project-issues-dev@eclipse.org
Date:   06/06/2014 11:13 AM
Subject:[cross-project-issues-dev] Switch from Luna RC2 to RC3 fails
all our Tycho run UI tests: Known issue?
Sent by:cross-project-issues-dev-boun...@eclipse.org



Hi,

hope cross-project-issues is the right list for this, but for us it's a
huge issue (none of our builds pass) and I am wondering whether any
other project has encountered this as well:

We use  as update site in
our builds. Now, as of today, i.e., the promotion of RC3 from staging to
said update site, Tycho fails to execute all of our UI tests. I have
opened Bug 436858 [1] to document my findings so far, but the short
version is that the UI tests all fail with the tycho-surefire-plugin
saying some along the lines of

> An error has occurred. See the log
file .../target/work/data/.metadata/.log.

with the log then containing

> !ENTRY org.eclipse.osgi 4 0 2014-06-06 09:17:04.074
> !MESSAGE Application error
> !STACK 1
> java.lang.NullPointerException
>at
org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine
$StylingPreferencesHandler.getPreferences(PartRenderingEngine.java:1500)
>at
org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine
$StylingPreferencesHandler.resetOverriddenPreferences
(PartRenderingEngine.java:1470)
>at
org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine
$StylingPreferencesHandler$1.handleEvent(PartRenderingEngine.java:1458)
>at org.eclipse.swt.widgets.EventTable.sendEvent
(EventTable.java:84)
>at org.eclipse.swt.widgets.Display.sendEvent
(Display.java:4487)
>at org.eclipse.swt.widgets.Display.sendEvent
(Display.java:4480)
>at org.eclipse.swt.widgets.Display.release(Display.java:3488)
>at org.eclipse.swt.graphics.Device.dispose(Device.java:249)
>at
org.eclipse.ui.internal.ide.application.IDEApplication.start
(IDEApplication.java:151)
>at
org.eclipse.tycho.surefire.osgibooter.UITestApplication.runApplication
(UITestApplication.java:31)
>at
org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.run
(AbstractUITestApplication.java:114)
>at
org.eclipse.tycho.surefire.osgibooter.UITestApplication.start
(UITestApplication.java:37)
>at org.eclipse.equinox.internal.app.EclipseAppHandle.run
(EclipseAppHandle.java:196)
>at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication
(EclipseAppLauncher.java:134)
>at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start
(EclipseAppLauncher.java:104)
>at org.eclipse.core.runtime.adaptor.EclipseStarter.run
(EclipseStarter.java:382)
>at org.eclipse.core.runtime.adaptor.EclipseStarter.run
(EclipseStarter.java:236)
>at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:57)
>at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:43)
>at java.lang.reflect.Method.invoke(Method.java:606)
>at org.eclipse.equinox.launcher.Main.invokeFramework
(Main.java:648)
>at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
>at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
>at org.eclipse.equinox.launcher.Main.main(Main.java:1438)

and possibly a complaint about an invalid thread access (SWTException).

Has anyone else seen this?

Best wishes,

Andreas

[1] 

--
Codetrails UG (haftungsbeschränkt)
The knowledge transfer company

Robert-Bosch-Str. 7, 64293 Darmstadt
Mobile: +49-170-811-3791
http://www.codetrails.com/

Managing Director: Dr. Marcel Bruch
Handelsregister: Darmstadt HRB 91940
___
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] Switch from Luna RC2 to RC3 fails all our Tycho run UI tests: Known issue?

2014-06-06 Thread Andreas Sewe 
Hi,

hope cross-project-issues is the right list for this, but for us it's a
huge issue (none of our builds pass) and I am wondering whether any
other project has encountered this as well:

We use  as update site in
our builds. Now, as of today, i.e., the promotion of RC3 from staging to
said update site, Tycho fails to execute all of our UI tests. I have
opened Bug 436858 [1] to document my findings so far, but the short
version is that the UI tests all fail with the tycho-surefire-plugin
saying some along the lines of

> An error has occurred. See the log file .../target/work/data/.metadata/.log.

with the log then containing

> !ENTRY org.eclipse.osgi 4 0 2014-06-06 09:17:04.074
> !MESSAGE Application error
> !STACK 1
> java.lang.NullPointerException
>   at 
> org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$StylingPreferencesHandler.getPreferences(PartRenderingEngine.java:1500)
>   at 
> org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$StylingPreferencesHandler.resetOverriddenPreferences(PartRenderingEngine.java:1470)
>   at 
> org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$StylingPreferencesHandler$1.handleEvent(PartRenderingEngine.java:1458)
>   at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
>   at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4487)
>   at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4480)
>   at org.eclipse.swt.widgets.Display.release(Display.java:3488)
>   at org.eclipse.swt.graphics.Device.dispose(Device.java:249)
>   at 
> org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:151)
>   at 
> org.eclipse.tycho.surefire.osgibooter.UITestApplication.runApplication(UITestApplication.java:31)
>   at 
> org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.run(AbstractUITestApplication.java:114)
>   at 
> org.eclipse.tycho.surefire.osgibooter.UITestApplication.start(UITestApplication.java:37)
>   at 
> org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
>   at 
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
>   at 
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
>   at 
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:382)
>   at 
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:236)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:606)
>   at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
>   at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
>   at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
>   at org.eclipse.equinox.launcher.Main.main(Main.java:1438)

and possibly a complaint about an invalid thread access (SWTException).

Has anyone else seen this?

Best wishes,

Andreas

[1] 

-- 
Codetrails UG (haftungsbeschränkt)
The knowledge transfer company

Robert-Bosch-Str. 7, 64293 Darmstadt
Mobile: +49-170-811-3791
http://www.codetrails.com/

Managing Director: Dr. Marcel Bruch
Handelsregister: Darmstadt HRB 91940
___
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] Intalling with java 6 cannot recover

2014-06-06 Thread Thomas Watson 
FYI, We are planning to fix for RC4.  Thanks for reporting the issue.

Tom





From:   Marc-André Laperle 
To: Cross project issues 
Date:   06/05/2014 05:14 PM
Subject:Re: [cross-project-issues-dev] Intalling with java 6 cannot
recover
Sent by:cross-project-issues-dev-boun...@eclipse.org



Thomas,

I think I managed to find reproducable steps, see:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=436758

Marc-Andre

On 14-06-05 04:54 PM, Thomas Watson wrote:


  I just tried and could not reproduce.  Installing CDT on Java 6,
  re-launching and having a look at the osgi> console showed the CDT
  bundles as INSTALLED (not resolved).  Relaunching with Java 7 allowed
  the CDT bundles to resolve.  I would double check that Java 7 is
  really being used.  Start with -console and issue the command:

  props | grep environment

  That should give you the following:

  org.osgi.framework.executionenvironment =
  
OSGi/Minimum-1.0,OSGi/Minimum-1.1,OSGi/Minimum-1.2,JRE-1.1,J2SE-1.2,J2SE-1.3,J2SE-1.4,J2SE-1.5,JavaSE-1.6,JavaSE-1.7


  Notice JavaSE-1.7 at the end.

  Tom



  Inactive hide details for Marc Khouzam ---06/05/2014
  02:54:27 PM---Sadly I did launch with -clean and it didn't
  help. Since it Marc Khouzam ---06/05/2014 02:54:27 PM---Sadly I did
  launch with -clean and it didn't help. Since it should be fixed in
  M7, we'll try to repr

  From: Marc Khouzam 
  To: "'Cross project issues'" 
  Date: 06/05/2014 02:54 PM
  Subject: Re: [cross-project-issues-dev] Intalling with java 6 cannot
  recover
  Sent by: cross-project-issues-dev-boun...@eclipse.org





  Sadly I did launch with –clean and it didn’t help.

  Since it should be fixed in M7, we’ll try to reproduce on another
  machine to make sure it is not my environment.

  From: cross-project-issues-dev-boun...@eclipse.org [
  mailto:cross-project-issues-dev-boun...@eclipse.org] On Behalf Of
  Thomas Watson
  Sent: Thursday, June 05, 2014 3:07 PM
  To: Cross project issues
  Subject: Re: [cross-project-issues-dev] Intalling with java 6 cannot
  recover



  This sounds like https://bugs.eclipse.org/bugs/show_bug.cgi?id=432485

  But that should have been fixed in M7.  I am curious if launching
  with -clean fixes the issue.  I would start with a bug against
  Equinox Framework if it is what I suspect (somehow the framework is
  not forcing a refresh of the system bundle to update its capabilities
  to include the Java 7 execution environment).

  Tom



  Inactive hide details for Marc Khouzam ---06/05/2014
  12:05:12 PM---Hi, I'm testing installing CDT on RC3. CDT
  requires Java 7.Marc Khouzam ---06/05/2014 12:05:12 PM---Hi, I'm
  testing installing CDT on RC3.  CDT requires Java 7.

  From: Marc Khouzam 
  To: "'cross-project-issues-dev@eclipse.org'" <
  cross-project-issues-dev@eclipse.org>
  Cc: Alvaro Sanchez-Leon 
  Date: 06/05/2014 12:05 PM
  Subject: [cross-project-issues-dev] Intalling with java 6 cannot
  recover
  Sent by: cross-project-issues-dev-boun...@eclipse.org






  Hi,

  I'm testing installing CDT on RC3.  CDT requires Java 7.
  My system switched to java 6 under my feet, so I ended up installing
  CDT using java 6.
  The install worked but when running, most CDT plugins didn't start
  and I got some errors due to java 6.
  I then switched back to java 7 and ran the already installed version.
  Surprisingly, things still failed but no errors reported.

  So, it looks like installing plugins that require a newer java than
  what is running is non-recoverable.

  Is this a bug I should report? If so, to what component?

  Thanks

  Marc
  ___
  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

[cross-project-issues-dev] Luna RC3 repository is available

2014-06-06 Thread David M Williams 
I've made the "RC3" repository visible under the build-in repository at 

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

The EPP packages will be available soon, if not already, from 

http://www.eclipse.org/downloads/index-developer.php

Happy testing! 

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