[
https://issues.apache.org/jira/browse/DERBY-3149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12555876#action_12555876
]
Kristian Waagan commented on DERBY-3149:
----------------------------------------
Is there already a variable for Java SE 5.0 compile classpath in the build
script(s)?
If not, are there any plans to introduce one?
I see there is a java15compile.classpath in the root build.xml, but as far as I
can tell, it is only set when using the new "autoprop" feature and I haven't
found any targets using it yet.
I see that many targets are using compile.classpath. This is currently set to
java14compile.classpath, and changing it would probably be a bad idea.
Last, I see that we require J2SE 5.0 or higher in BUILDING.txt. Don't we need a
variable for this "default" compile classpath?
In my case I'm using J2SE 5.0 features in some tests, and I would like these
tests to be built when JDK 1.5 is available. Currently they are only built if
JDK 1.6 is available.
> Add ant targets for building and running the package private tests against
> the classes directories
> --------------------------------------------------------------------------------------------------
>
> Key: DERBY-3149
> URL: https://issues.apache.org/jira/browse/DERBY-3149
> Project: Derby
> Issue Type: Sub-task
> Components: Build tools, Test
> Affects Versions: 10.4.0.0
> Reporter: Kristian Waagan
> Assignee: Kristian Waagan
> Priority: Minor
> Fix For: 10.4.0.0
>
> Attachments: derby-3149-1a.diff, derby-3149-1a.stat,
> derby-3149-1b.diff, derby-3149-2a-conditional_compilation_fix.diff,
> derby-3149-2b-conditional_compilation_fix.diff
>
>
> Create ant targets in build.xml to compile and run the package private tests.
> The first step will be to run the tests against the classes directories.
> Implementing a solution that runs against jars is not technically difficult,
> it just brings a host of decisions to be taken... Maybe even more important,
> does running against the jars add any value?
> The compile will be included in the 'all' target to test the implementation.
> Feel free to post your concerns if you think building the package private
> tests should be a manual action only.
> The tests will also be run as part of junit-all / junitreport.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
