Please vote on whether we should require that developers use a Java 5
(or later) compiler in order to build Derby. This means that the shell
window running the build should have its JAVA_HOME pointed at a Java 5
or later jdk and the corresponding javac should be what's visible on
PATH. The prac
Rick Hillegas <[EMAIL PROTECTED]> writes:
> Please vote on whether we should require that developers use a Java 5
> (or later) compiler in order to build Derby.
+1
--
Knut Anders
+1
Rick Hillegas wrote:
Please vote on whether we should require that developers use a Java 5
(or later) compiler in order to build Derby. This means that the shell
window running the build should have its JAVA_HOME pointed at a Java 5
or later jdk and the corresponding javac should be what's
If I only have jdk1.5 environment will the build succeed, and if so will
it identify if I have somehow used a jdk1.5 specific library function in
a "non-optional" part of the code?
How is optional vs. non-optional code specified? Is this an ant xml
file property in the directory for the code?
+1
On 9/26/07, Rick Hillegas <[EMAIL PROTECTED]> wrote:
> +1
>
> Rick Hillegas wrote:
> > Please vote on whether we should require that developers use a Java 5
> > (or later) compiler in order to build Derby. This means that the shell
> > window running the build should have its JAVA_HOME pointed
Mike Matrigali wrote:
If I only have jdk1.5 environment will the build succeed, and if so will
it identify if I have somehow used a jdk1.5 specific library function in
a "non-optional" part of the code?
Hi Mike,
You will still need jdk 1.4 and you will still need to set j14lib in
your ant.prop
On 9/26/07, Rick Hillegas <[EMAIL PROTECTED]> wrote:
> Mike Matrigali wrote:
> > If I only have jdk1.5 environment will the build succeed, and if so will
> > it identify if I have somehow used a jdk1.5 specific library function in
> > a "non-optional" part of the code?
> Hi Mike,
>
> You will still
Andrew McIntyre wrote:
On 9/26/07, Rick Hillegas <[EMAIL PROTECTED]> wrote:
Mike Matrigali wrote:
If I only have jdk1.5 environment will the build succeed, and if so will
it identify if I have somehow used a jdk1.5 specific library function in
a "non-optional" part of the code?
+1
Dag
Rick Hillegas <[EMAIL PROTECTED]> writes:
> Please vote on whether we should require that developers use a Java 5
> (or later) compiler in order to build Derby. This means that the shell
> window running the build should have its JAVA_HOME pointed at a Java 5
> or later jdk and the corresponding j
Rick Hillegas <[EMAIL PROTECTED]> writes:
Please vote on whether we should require that developers use a Java 5
(or later) compiler in order to build Derby. This means that the shell
window running the build should have its JAVA_HOME pointed at a Java 5
or later jdk and the corresponding javac s
The polls have closed. The developer community has approved requiring
that developers use a Java 5 or later compiler in order to build Derby.
+1 votes:
Knut Anders Hatlen
Rick Hillegas
David Van Couvering
Dag Wanvik
Dyre Tjeldvoll
Dan Debrunner
No other votes were cast.
Regards,
-Rick
Rick
Daniel John Debrunner wrote:
Seems that it might be possible with this to start using some 1.5
language constructs in Derby's code: those that compile down to standard
byte code. This would be by using -source 1.5 -target 1.4 in the
build.xml files.
Be *very* careful about what 1.5 language f
Seems that it might be possible with this to start using some 1.5
language constructs in Derby's code: those that compile down to
standard byte code. This would be by using -source 1.5 -target 1.4 in
the build.xml files.
Be *very* careful about what 1.5 language features you start using in
yo
Thomas Nielsen wrote:
Daniel John Debrunner wrote:
Seems that it might be possible with this to start using some 1.5
language constructs in Derby's code: those that compile down to
standard byte code. This would be by using -source 1.5 -target 1.4 in
the build.xml files.
Be *very* careful ab
Daniel John Debrunner wrote:
Thomas Nielsen wrote:
Daniel John Debrunner wrote:
Seems that it might be possible with this to start using some 1.5
language constructs in Derby's code: those that compile down to
standard byte code. This would be by using -source 1.5 -target 1.4 in
the build.xml
Daniel John Debrunner <[EMAIL PROTECTED]> writes:
> Never mind:
>
>> $JAVA_HOME/bin/javac -target 1.4 -source 1.5
> javac: source release 1.5 requires target release 1.5
It seems -target jsr14 is not officially supported for the Sun JDK, at least it
is not
listed in the javac documentation as a
Dag H. Wanvik wrote:
It seems -target jsr14 is not officially supported for the Sun JDK, at least it
is not
listed in the javac documentation as a valid target:
http://java.sun.com/j2se/1.5.0/docs/tooldocs/solaris/javac.html#options
True.
From what I can tell -target jsr14 was introduced dur
18 matches
Mail list logo
