[ 
http://issues.apache.org/jira/browse/DERBY-1526?page=comments#action_12421792 ] 
            
Andrew McIntyre commented on DERBY-1526:
----------------------------------------

The only information expected to be in ${user.home}/ant.properties for the 
Derby build is the location of the runtime java libraries that are accessible 
to the current user. These runtime classes can (and should) be static across 
Derby versions. i.e. the versions of Java that you use to build any particular 
version of Derby should consistently build multiple versions of Derby. There 
shouldn't be any information in ${user.home}/ant.properties that is specific to 
a specific version of Derby.

With the current setup, I can specify the locations of the multiple versions of 
the runtime classes needed to build Derby once for each machine/user where I am 
building in the user's ant.properties. Then, I can build 10.0, 10.1, and 10.2 
without needing to change anything but the directory where I've checked out the 
source. The requirements on Mac OS X for the content in ant.properties is 
somewhat different, as noted in BUILDING.txt, but once set up, I can build 
Derby 10.0, 10.1, and the trunk without needing to set up a separate properties 
file for each individual checkout of the source. I find this very handy.

That said, I can understand the desire not to introduce a dependency on a 
user-space file. I think there is room for improvement here if we also sourced 
a file from ${basedir} in addition to the user.home, in case a user wants to 
have these base properties sourced from a file that is specific to a particular 
checkout of Derby.

As far as the affects version, there currently is not a way to track specific 
Subversion revisions in JIRA. Since it looks like you are working with the 
trunk, we are tracking the current trunk version as 10.2.0.0 in JIRA. For the 
other versions, the latest released 10.1 version is 10.1.3.1 and the latest 
released 10.0 version is 10.0.2.1.

> building does not need to use ${user.home} and it should not do so
> ------------------------------------------------------------------
>
>                 Key: DERBY-1526
>                 URL: http://issues.apache.org/jira/browse/DERBY-1526
>             Project: Derby
>          Issue Type: Bug
>          Components: Build tools
>            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

        

Reply via email to