logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 17862] - Version.getVersion() method requested
Date Thu, 02 Mar 2006 18:33:53 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=17862>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=17862


carnold@apache.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|FIXED                       |




------- Additional Comments From carnold@apache.org  2006-03-02 19:33 -------
Sorry I came to this late.  Some additional references:

http://java.sun.com/j2se/1.4.2/docs/guide/versioning/spec/versioningTOC.html
http://www.javaworld.com/javaworld/jw-09-2002/jw-0920-jpvs.html

The proposed class appears to duplicate some of the functionality of the Java Product Versioning

specification but lacks some of its nuances.  

The implementation version of log4j has been included in the log4j.jar manifest in both the
1.2 and 1.3 
branches.  The following code should be able to retrieve the info:

String log4jImpl = org.lang.Package.getPackage("org.apache.log4j").getImplementationVersion();

The Versioning specification provides two distinct versioning identification, the implementation
and the 
specification.  log4j has only included implementation version info (which is likely a good
thing).  The 
specs cover this in more detail but the idea is that there is no specified format for implementation

version identifiers and no implied compatibility between implementations unless their implementation

strings are precisely identical.  Specifications have a specified format (1.2.3....) where
compatibility 
between specifications is inferred in a typical manner.

Once the 1.3 API's have firmed up, it may be desirable to add a specification version to the
manifest 
file, so you could task things like:

boolean isLog4J131_compatible = Package.getPackage("org.apache.log4j").isCompatibleWith("1.3.1");


-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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


Mime
View raw message