[ http://issues.apache.org/jira/browse/DERBY-1526?page=comments#action_12421874 ] Rick Hillegas commented on DERBY-1526: --------------------------------------
${user.home}/ant.properties also holds configuration variables needed to run the ant-based compatibility tests. I don't have strong religion about where we should keep user-specific environment variables. However, I'd like to keep these variables in one place and not have to clone them. Here's what I like about the current arrangement: all ant-based scripts look for environment variables in a canonical place. As long as we preserve that behavior, I'm happy. > 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