Dinesh Patil wrote:
> Carla Mott wrote:
>
>> It is a bit of a manual process now to go to the download page
>> and look to see what the next promoted build number will be.
>>
>> Dinesh,
>>
>> Any way we can make this info available in the workspace? What
>> would it take and is it worth it?
>
>
> Currently build_id varible is present in appserv-core/build.properties
> which is overriden by nightly build by passing -Dbuild_id=<latest>
> So we can have actual build_id in glassfish/bootstrap module in any
> common properties file (e.g. we can have this in
> glassfish.subcomponent.properties), which is accessed to all modules as
> this module needs to be checked out for any workspace command. We can
> update this file once build is promoted, so developers can +1 to this in
> their checkin comments/target milestone.
This seems better. I assume I always have to update the bootstrap
module before I can do a commit.
If this property is going to be updated automatically, you might find
it more convenient to put it in a file of its own, so it can never
conflict with manual updates to build.properties.