db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-5485) Simplify PropertySetter so that it is less brittle and easier to maintain.
Date Fri, 04 Nov 2011 21:49:51 GMT

    [ https://issues.apache.org/jira/browse/DERBY-5485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13144379#comment-13144379
] 

Kathey Marsden commented on DERBY-5485:
---------------------------------------

I did not review, but did try out building with the   derby-5485-01-ag-changeJDBClevel.diff
patch and ran a single test.  I was able to build fine with both my previously posted local.properties
and no local.properties file. Thanks Rick!


  
                
> Simplify PropertySetter so that it is less brittle and easier to maintain.
> --------------------------------------------------------------------------
>
>                 Key: DERBY-5485
>                 URL: https://issues.apache.org/jira/browse/DERBY-5485
>             Project: Derby
>          Issue Type: Improvement
>          Components: Build tools
>    Affects Versions: 10.9.0.0
>            Reporter: Rick Hillegas
>         Attachments: derby-5485-01-af-simplifyPlusJavadoc.diff, derby-5485-01-ag-changeJDBClevel.diff
>
>
> The PropertySetter task sets up classpath variables so that the build can take advantage
of JVM-specific class libraries. Using those libraries makes it possible for the compiler
to flag code which is supposed to run on less capable platforms but which calls methods from
later JVMs. This is a very tricky problem and we seem to have reached consensus that it requires
too much effort to make PropertySetter run correctly in all of the build environments which
Derby developers use. I will attach a proposal for how to simplify PropertySetter so that
it requires less effort to maintain.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message