jakarta-bsf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rony G. Flatscher" <Rony.Flatsc...@wu-wien.ac.at>
Subject Re: A suggestion on versioning information ....
Date Sun, 22 Jan 2006 12:41:03 GMT

Ulf Dittmer wrote:

> Not so much for an end user running BSF-based code, but for the 
> developers of BSF engines. An engine may support more than one version 
> of BSF, but differentiate its behavior based on the capability of BSF.
>
> On 22.01.2006, at 06:37, Henri Yandell wrote:
>
>> Basically, is there a need to know the version at runtime?
>
In addition, it makes it easier than going via the manifest file, which 
in cases where BSF got repackaged may not be available or contain any 
further BSF-related version information at all. (Using version infos 
and/or build dates as part of file-names is rather fragile and hence 
error-prone.) Having an easy way to access that vital information may 
come in very handy as well for some use-cases, e.g. is there a newer, 
compatible - same major version number as the one which is distributed 
via the app -  BSF already installed on the system etc.

Getting the version info from a public static method located in 
BSFManager should make it easy on anyone to get at the "real" version 
number.

---rony



---------------------------------------------------------------------
To unsubscribe, e-mail: bsf-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: bsf-dev-help@jakarta.apache.org


Mime
View raw message