Max Berger wrote:
Hi Max,
Vincent,
Am 09.06.2008 um 20:01 schrieb Vincent Hennebert:
There’s a point that I’d like to further discuss: why wouldn’t we
implement Retroweaver/Retrotranslator in the Trunk? If we go the
cautious route, that is if we run the test suite on a 1.4 jvm after each
i
Vincent,
Am 09.06.2008 um 20:01 schrieb Vincent Hennebert:
There’s a point that I’d like to further discuss: why wouldn’t we
implement Retroweaver/Retrotranslator in the Trunk? If we go the
cautious route, that is if we run the test suite on a 1.4 jvm after
each
introduction of a 1.5 feature
at all IMO... Or this would be a very short-lived branch
> (no more than a few weeks), just the time to test
> Retroweaver/translator.
>
> Thanks,
> Vincent
>
>
> Vincent Hennebert wrote:
> > Hi Guys,
> >
> > I would like to raise this topic again: what
few weeks), just the time to test
Retroweaver/translator.
Thanks,
Vincent
Vincent Hennebert wrote:
> Hi Guys,
>
> I would like to raise this topic again: what about switching to Java 1.5
> as a minimum requirement?
>
> The End of Life transition period for Java 1.4 will
Guys,
I would like to raise this topic again: what about switching to Java 1.5
as a minimum requirement?
The End of Life transition period for Java 1.4 will end on the 30th of
October 2008 [1]. The next version of FOP (after 0.95) will probably not
have been released by this time, so we could
Max Berger wrote:
I have to disagreee. AAMOF, java 1.5 is ONLY supported on a select
number of plattforms, mainly the ones Sun provides the JDK for (or is
licensed).
Well, gcj claims 1.5 compatibility and can be compiled on
almost anything. My personal experience on a Debian AMD64
platform is t
Peter B. West wrote:
Jess Holle wrote:
Java 5 runs on HPUX and AIX machines as well -- as well as on Solaris
x86. When you've got Windows, Mac OS X, x86 Linux, Solaris, HPUX,
and AIX covered, I'd say that's pretty good. The other platforms
are, er, odd balls.
The question is whether you ho
Jess Holle wrote:
Max Berger wrote:
Jess Holle schrieb:
As of October of this year anything prior to Java 5 will be officially
unsupported by Sun except where you have a paid support contract with
them (including that for Solaris). Add to that the fact that Java 1.4
is so limiting for so man
Max Berger wrote:
Jess Holle schrieb:
As of October of this year anything prior to Java 5 will be officially
unsupported by Sun except where you have a paid support contract with
them (including that for Solaris). Add to that the fact that Java 1.4
is so limiting for so many things and Java
On Jun 5, 2008, at 19:26, Andreas Delmelle wrote:
On Jun 5, 2008, at 17:46, Vincent Hennebert wrote:
Hi Guys,
I would like to raise this topic again: what about switching to
Java 1.5
as a minimum requirement?
No objection from me. +1 on moving forward with this in the trunk.
Just to
Just stumbled upon this...
http://en.wikipedia.org/wiki/Comparison_of_backporting_tools
Retrotranslator looks to have a more fully implemented feature set. Maybe we
should try both.
Adrian.
Max Berger wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dear Fop-devs,
Jess Holle schrieb:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dear Fop-devs,
Jess Holle schrieb:
> As of October of this year anything prior to Java 5 will be officially
> unsupported by Sun except where you have a paid support contract with
> them (including that for Solaris). Add to that the fact that Java 1.
s right.
> -0.5 (no veto) to moving to Java 1.5 before Oct 2008.
> +1 to making experiments with Retroweaver (but please not in Trunk).
>
> On 05.06.2008 17:46:07 Vincent Hennebert wrote:
>
>
> Hi Guys,
>
> I would like to raise this topic again: what about switching to J
+1 to moving to Java 1.5 when the time is right.
-0.5 (no veto) to moving to Java 1.5 before Oct 2008.
+1 to making experiments with Retroweaver (but please not in Trunk).
On 05.06.2008 17:46:07 Vincent Hennebert wrote:
Hi Guys,
I would like to raise this topic again: what about switching t
008 17:46:07 Vincent Hennebert wrote:
>> Hi Guys,
>>
>> I would like to raise this topic again: what about switching to Java 1.5
>> as a minimum requirement?
>>
>> The End of Life transition period for Java 1.4 will end on the 30th of
>> October 2008 [1].
Vincent Hennebert wrote:
Hi Guys,
I would like to raise this topic again: what about switching to Java 1.5
as a minimum requirement?
Hi Vincent,
I'm happy to allow the use of generics in trunk code if retroweaver is
used to maintain Java 1.4 support. I don't think the time i
.5 (no veto) to moving to Java 1.5 before Oct 2008.
+1 to making experiments with Retroweaver (but please not in Trunk).
On 05.06.2008 17:46:07 Vincent Hennebert wrote:
> Hi Guys,
>
> I would like to raise this topic again: what about switching to Java 1.5
> as a minimum requir
e past and it
seemed to work well, but it would interesting to hear from anyone
who has any hands on experience with using it.
+1 from me.
Adrian.
Vincent Hennebert wrote:
Hi Guys,
I would like to raise this topic again: what about switching to
Java 1.5
as a minimum requirement?
The E
On Jun 5, 2008, at 17:46, Vincent Hennebert wrote:
Hi Guys,
I would like to raise this topic again: what about switching to
Java 1.5
as a minimum requirement?
No objection from me. +1 on moving forward with this in the trunk.
Andreas
t and
it seemed to work well, but it would interesting to hear from anyone who has any hands on experience
with using it.
+1 from me.
Adrian.
Vincent Hennebert wrote:
Hi Guys,
I would like to raise this topic again: what about switching to Java 1.5
as a minimum requirement?
The End of
Hi Guys,
I would like to raise this topic again: what about switching to Java 1.5
as a minimum requirement?
The End of Life transition period for Java 1.4 will end on the 30th of
October 2008 [1]. The next version of FOP (after 0.95) will probably not
have been released by this time, so we could
21 matches
Mail list logo
