Alan Williamson wrote:
> Jeanfrancois Arcand wrote:
>>> Do we currently include a release number of Grizzly within the
>>> grizzly jar file(s) ?
>>
>> The maven artifact (jar) contains, under the META-folder, that
>> information. Do you think that's enough?
>
> is there any milage in making that information available via a class
> call?
>
> public class Grizzly {
> public static int Grizzly.getMajorVersion(){ return 1; }
> public static int Grizzly.getMinorVersion(){ return 7; }
> }
I think this idea has some merit to it.
I could see a case where an application may want to do something
different based on the version of Grizzly. Having this information
available in a class would probably save some ugly implementation from a
user of Grizzly.
Perhaps we should consider adding another API that compares a major
version / minor version with the current version of Grizzly? i.e.
public class Grizzly {
final private static int major = 1;
final private static int minor = 7;
public static int Grizzly.getMajorVersion(){
return this.major;
}
public static int Grizzly.getMinorVersion(){
return minor;
}
public static boolean equalVersion(int major, int minor) {
if (minor == this.minor && major == this.major) {
return true;
return false;
}
charlie ...
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: users-help_at_grizzly.dev.java.net
>
--
Charlie Hunt
Java Performance Engineer
<http://java.sun.com/docs/performance/>