You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Rick Hillegas (JIRA)" <ji...@apache.org> on 2008/05/21 20:43:55 UTC

[jira] Updated: (DERBY-3684) Wire the vti demo into the build.

     [ https://issues.apache.org/jira/browse/DERBY-3684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rick Hillegas updated DERBY-3684:
---------------------------------

    Attachment: derby-3684-02-aa-adjustREADME.diff
                derby-3684-01-aa-wireInDemoCode.diff

Attaching and committing two patches:

derby-3684-01-aa-wireInDemoCode.diff wires the vti demo code into the standard Derby build. Committed at subversion revision 658805. Touches the following files:

M      java/demo/build.xml
M      build.xml

derby-3684-02-aa-adjustREADME.diff edits the demo's README file to indicate that the code is now built as part of the standard Derby build. Committed at subversion revision 658806. Touches the following file:

M      java/demo/vtis/README


> Wire the vti demo into the build.
> ---------------------------------
>
>                 Key: DERBY-3684
>                 URL: https://issues.apache.org/jira/browse/DERBY-3684
>             Project: Derby
>          Issue Type: Improvement
>          Components: Build tools
>            Reporter: Rick Hillegas
>            Assignee: Rick Hillegas
>            Priority: Minor
>             Fix For: 10.5.0.0
>
>         Attachments: derby-3684-01-aa-wireInDemoCode.diff, derby-3684-02-aa-adjustREADME.diff
>
>
> The classes under java/demo/vtis were excluded from the standard build because they relied on Java 5 features. Now that we require that people use a Java 5 (or later) compiler, we can wire this code into the standard build just as the rest of the demo code is wired into the standard build.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Re: [jira] Updated: (DERBY-3684) Wire the vti demo into the build.

Posted by Rick Hillegas <Ri...@Sun.COM>.
Hi Dag,

Right. If you omit a deprecation setting in your ant.properties, the 
build defaults to "deprecation=on" and you see a bunch of deprecation 
warnings, largely on our implementations of JDBC interfaces. The demo 
classes add some more implementations of ResultSet and so generate 
another raft of these warnings. You can throttle them by setting 
"deprecation=off" in your ant.properties.

Regards,
-Rick

Dag H. Wanvik wrote:
> Hi Rick,
>
> Rick Hillegas <Ri...@Sun.COM> writes:
>
>   
>> Dag H. Wanvik wrote:
>>     
>>> Just a nit, I see more compiler warning after this fix (building with
>>> Java 1.6 or 1.5 made no difference for me) due to the ResultSet method
>>> deprecations. I guess this can't be suppressed..?
>>>       
>
> I did not use the -quiet option; this is the first lines of what I saw
>
> compile-vtidemo:
>     [javac] Compiling 18 source files to /export/home/tmp/derby/sb/sb1/classes
>     [javac] /export/home/tmp/derby/sb/sb1/java/demo/vtis/java/org/apache/derbyDemo/vtis/core/VTITemplate.java:354: warning: [deprecation] getUnicodeStream(java.lang.String) in java.sql.ResultSet has been deprecated
>     [javac]     public java.io.InputStream getUnicodeStream(String columnName) throws SQLException {
>     [javac]                                ^
>     [javac] /export/home/tmp/derby/sb/sb1/java/demo/vtis/java/org/apache/derbyDemo/vtis/core/VTITemplate.java:300: warning: [deprecation] getBigDecimal(java.lang.String,int) in java.sql.ResultSet has been deprecated
>     [javac]     public BigDecimal getBigDecimal(String columnName, int scale) throws SQLException {
>     [javac]                       ^
>     [javac] /export/home/tmp/derby/sb/sb1/java/demo/vtis/java/org/apache/derbyDemo/vtis/core/VTITemplate.java:209: warning: [deprecation] getUnicodeStream(int) in java.sql.ResultSet has been deprecated
>
>     etc.
>
> but I see there are many other similar ones as well in existing code
> so I guess it's OK. I had deprecation off in my ant.properties though.
>
> Dag
>
>   
>> which java
>>     
> /usr/local/java/jdk1.5/bin/java
>   
>> cat ant.properties
>>     
> j13lib=/usr/local/java/jdk1.3/jre/lib
> j14lib=/usr/local/java/j2sdk1.4.2_13/jre/lib
> j15lib=/usr/local/java/jdk1.5/jre/lib
> jdk16=/usr/local/java/jdk1.6.0
> proceed=false
> sane=true
> debug=true
> #jsr169compile.classpath=
>
> #java15compile.classpath=/usr/local/java/jdk1.6.0/jre/lib/rt.jar
> #junit=/usr/local/share/java/junit3.8.2/junit.jar
> #servlet24= ?? (see build.xml...)
> #ant.library.dir=/usr/local/share/java/apache-ant-1.6.5/lib
> #deprecation=on
>   


Re: [jira] Updated: (DERBY-3684) Wire the vti demo into the build.

Posted by "Dag H. Wanvik" <Da...@Sun.COM>.
Hi Rick,

Rick Hillegas <Ri...@Sun.COM> writes:

> Dag H. Wanvik wrote:
>> Just a nit, I see more compiler warning after this fix (building with
>> Java 1.6 or 1.5 made no difference for me) due to the ResultSet method
>> deprecations. I guess this can't be suppressed..?

I did not use the -quiet option; this is the first lines of what I saw

compile-vtidemo:
    [javac] Compiling 18 source files to /export/home/tmp/derby/sb/sb1/classes
    [javac] /export/home/tmp/derby/sb/sb1/java/demo/vtis/java/org/apache/derbyDemo/vtis/core/VTITemplate.java:354: warning: [deprecation] getUnicodeStream(java.lang.String) in java.sql.ResultSet has been deprecated
    [javac]     public java.io.InputStream getUnicodeStream(String columnName) throws SQLException {
    [javac]                                ^
    [javac] /export/home/tmp/derby/sb/sb1/java/demo/vtis/java/org/apache/derbyDemo/vtis/core/VTITemplate.java:300: warning: [deprecation] getBigDecimal(java.lang.String,int) in java.sql.ResultSet has been deprecated
    [javac]     public BigDecimal getBigDecimal(String columnName, int scale) throws SQLException {
    [javac]                       ^
    [javac] /export/home/tmp/derby/sb/sb1/java/demo/vtis/java/org/apache/derbyDemo/vtis/core/VTITemplate.java:209: warning: [deprecation] getUnicodeStream(int) in java.sql.ResultSet has been deprecated

    etc.

but I see there are many other similar ones as well in existing code
so I guess it's OK. I had deprecation off in my ant.properties though.

Dag

> which java
/usr/local/java/jdk1.5/bin/java
> cat ant.properties
j13lib=/usr/local/java/jdk1.3/jre/lib
j14lib=/usr/local/java/j2sdk1.4.2_13/jre/lib
j15lib=/usr/local/java/jdk1.5/jre/lib
jdk16=/usr/local/java/jdk1.6.0
proceed=false
sane=true
debug=true
#jsr169compile.classpath=

#java15compile.classpath=/usr/local/java/jdk1.6.0/jre/lib/rt.jar
#junit=/usr/local/share/java/junit3.8.2/junit.jar
#servlet24= ?? (see build.xml...)
#ant.library.dir=/usr/local/share/java/apache-ant-1.6.5/lib
#deprecation=on

Re: [jira] Updated: (DERBY-3684) Wire the vti demo into the build.

Posted by Rick Hillegas <Ri...@Sun.COM>.
Dag H. Wanvik wrote:
> Just a nit, I see more compiler warning after this fix (building with
> Java 1.6 or 1.5 made no difference for me) due to the ResultSet method
> deprecations. I guess this can't be suppressed..?
>
> Dag
>   
I compile (with Java 5 on Mac OS X) using this command

ant -quiet all

That produces this output for me:

     [java] Warning: Lookahead adequacy checking not being performed 
since option LOOKAHEAD is more than 1.  Set option FORCE_LA_CHECK to 
true to force checking.
     [java] Warning: ParseException.java: File is obsolete.  Please 
rename or delete this file so that a new one can be generated for you.
     [java] Warning: Token.java: File is obsolete.  Please rename or 
delete this file so that a new one can be generated for you.
     [java] Warning: CharStream.java: File is obsolete.  Please rename 
or delete this file so that a new one can be generated for you.
    [javac] Note: 
/Users/rh161140/derby/mainline/trunk/java/engine/org/apache/derby/jdbc/EmbeddedDriver.java 
uses or overrides a deprecated API.
    [javac] Note: Recompile with -Xlint:deprecation for details.
    [javac] Note: Some input files use or override a deprecated API.
    [javac] Note: Recompile with -Xlint:deprecation for details.
    [javac] Note: Some input files use or override a deprecated API.
    [javac] Note: Recompile with -Xlint:deprecation for details.
    [javac] Note: 
/Users/rh161140/derby/mainline/trunk/java/testing/org/apache/derbyTesting/functionTests/util/ManyMethods.java 
uses or overrides a deprecated API.
    [javac] Note: Recompile with -Xlint:deprecation for details.
    [javac] Note: 
/Users/rh161140/derby/mainline/trunk/java/testing/org/apache/derbyTesting/functionTests/tests/jdbcapi/ParameterMappingTest.java 
uses or overrides a deprecated API.
    [javac] Note: Recompile with -Xlint:deprecation for details.
    [javac] Note: Some input files use or override a deprecated API.
    [javac] Note: Recompile with -Xlint:deprecation for details.
    [javac] Note: Some input files use unchecked or unsafe operations.
    [javac] Note: Recompile with -Xlint:unchecked for details.
    [javac] Note: 
/Users/rh161140/derby/mainline/trunk/java/testing/org/apache/derby/impl/drda/TestProto.java 
uses unchecked or unsafe operations.
    [javac] Note: Recompile with -Xlint:unchecked for details.

Is that what you see?

Thanks,
-Rick

Re: [jira] Updated: (DERBY-3684) Wire the vti demo into the build.

Posted by "Dag H. Wanvik" <Da...@Sun.COM>.
Just a nit, I see more compiler warning after this fix (building with
Java 1.6 or 1.5 made no difference for me) due to the ResultSet method
deprecations. I guess this can't be suppressed..?

Dag