Ian,
Comments below.
On 03/09/2013 3:01 AM, Ian Bull wrote:
On Sat, Aug 31, 2013 at 12:07 AM, Ed Merks ed.me...@gmail.com
mailto:ed.me...@gmail.com wrote:
John,
Please me be equally provocative.
Hi everyone, before we declare thermonuclear war on each other, let's
take a step
Hi Grégoire,
The editor validated, so I hope the build will pass too. ATL and Acceleo
have now been reenabled for Luna, though that will only be useful for M2
now.
Laurent Goubet
Obeo
On 02/09/2013 16:34, Laurent Goubet wrote:
Disabling all projects every year will always cause such issues
Hi Szymon
Your list omits the 'culprit'.
It is org.eclipse.osgi.util.NLS that is now Java 6 putting paid to all
attempts at internationalization with Java 5.
Regards
Ed Willink
On 02/09/2013 16:41, Szymon Ptaszkiewicz wrote:
See
Does anybody else have problems connecting to [1]? I've got read timeout
exceptions since yesterday.
The Sandbox Hudson seems to have some issues too. I cannot retrigger the job
[2] for example.
[1] http://maven.eclipse.org/nexus/content/repositories/milestone-indigo
[2]
On 09/03/2013 02:30 PM, Ken Lee wrote:
The Sandbox Hudson seems to have some issues too. I cannot retrigger
the job [2] for example.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=416393
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat http://www.jboss.org/tools
My blog
I probably should have mentioned, there are several bugs we are still
trying to work through, where the Tycho/Maven build picks a different
compiler level than the way PDE used to it ... and not always in the way
we intend, for example,
https://bugs.eclipse.org/bugs/show_bug.cgi?id=415116
Sorry for not communicating this aspect of the Equinox Framework changes in
Luna. Obviously we need to spell out the VM requirements clearly for the
Equinox framework being included in Luna. the NLS class is part of the
Equinox framework which has moved up to requiring Java 6.
Sorry for the
I agree. Let's figure out how to publicly and formally drop support for Java
5. Sun/Oracle discontinued public support in 2009!
From
http://en.wikipedia.org/wiki/Java_version_history#J2SE_5.0_.28September_30.2
C_2004.29
J2SE 5.0 entered its end-of-public-updates period on April 8, 2008
Hi
I'm sorry John but you are dodging the issue. There is far too much
this is what we do, and very little of this is what we require.
Most of the Eclipse SDK is "pure" Java code and has no direct
dependence on the underlying operating system. The chief
Hi all,
I just did something I don't really understand on the aggregation
repository, and pushed a merging commit (
http://git.eclipse.org/c/simrel/org.eclipse.simrel.build.git/commit/?h=Kepler_maintenanceid=0caf9d67fc9d0d0bdcc18485fbb3f1181387d565
) along with my real commit, as a result I
I think you dodged the answer :). If you use Java 5, you're have no guarantees.
We could change org.eclipse.* to 1.6, but that would be a huge effort for
little gain.
From: Ed Willink e...@willink.me.ukmailto:e...@willink.me.uk
Reply-To: Cross project issues
I can't think of any way to be clearer than I already have. The platform
requires Java 6, and it has required Java 6 for several years. Next time I
do a plan update I will try to make that even clearer.
John
From: Ed Willink e...@willink.me.uk
To: Cross project issues
And this is exactly why a granular approach to supported targets is a bad
idea. While it does offer some more flexibility in certain situations, it
causes massive confusion as to what's supported overall.
The decisions on what targets to support are rarely made on bundle-by-bundle
basis
Hi
I must be very dense. Where does it say "The platform requires Java 6".
Regards
Ed Willink
On 03/09/2013 17:19, John Arthorne
wrote:
I can't think of any
way to be clearer
than I already
He didn't. He said that the platform doesn't support java5:
Since Platform 3.8 it has certainly been impossible to run the complete platform
using Java 5 due to Jetty dependency on Java 6 (and possibly other bundles).
On 03/09/2013 12:34 PM, Ed Willink wrote:
Hi
I must be very dense. Where
15 matches
Mail list logo
