[
http://issues.apache.org/jira/browse/DERBY-1526?page=comments#action_12421881 ]
Daniel John Debrunner commented on DERBY-1526:
----------------------------------------------
Andrew wrote:
- These runtime [Java] classes can (and should) be static across Derby
versions.
That's not true, at least the "and should" piece. I may choose to build
different Derby codelines with different JDK setups. I do this today either
using IBM's SDK's or SUn's JDKs.
> build should be able to locate the Java runtime libraries from properties not
> sourced from ${user.home}, but inside the current subversion checkout.
> ----------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-1526
> URL: http://issues.apache.org/jira/browse/DERBY-1526
> Project: Derby
> Issue Type: Improvement
> Components: Build tools
> Affects Versions: 10.2.0.0
> Reporter: Ray Kiddy
> Priority: Minor
>
> I think it is problemmatic that the Derby build process makes use of, for
> example, ${user.home}/ant.properties.
> I would actually like to be able to build multiple versions of Derby. I also
> cannot see what is gained by relying on the user's home directory in this
> manner. All of this information could be put into a configuration that can be
> kept in the project directory. That would work just fine.
> By the way, I am looking at the top-of-tree code. How do I refer to that in
> the "Affects Version" box above? This version is 422938.
> thanx - ray
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
