Re: Logging the Java version

2014-09-18 Thread Ralph Goers
I think I misunderstood you. Yes, you can get java.vm.version and the like as system properties but they may not be completely formatted as Gary wishes. On Sep 18, 2014, at 4:38 PM, Ralph Goers wrote: > It isn't a system property > > Sent from my iPad > > On Sep 18, 2014, at 2:41 PM, Matt Si

Re: Logging the Java version

2014-09-18 Thread Ralph Goers
It isn't a system property Sent from my iPad > On Sep 18, 2014, at 2:41 PM, Matt Sicker wrote: > > Wouldn't this all be available through the ${sys:*} lookup variables? > >> On 18 September 2014 12:56, Ralph Goers wrote: >> I would recommend adding it as a special Lookup just like hostname is

Re: Logging the Java version

2014-09-18 Thread Matt Sicker
Wouldn't this all be available through the ${sys:*} lookup variables? On 18 September 2014 12:56, Ralph Goers wrote: > I would recommend adding it as a special Lookup just like hostname is. > Then in your pattern layout you just need to specify the header as > ${java-version} or ${java-short-ve

Re: Logging the Java version

2014-09-18 Thread Ralph Goers
I would recommend adding it as a special Lookup just like hostname is. Then in your pattern layout you just need to specify the header as ${java-version} or ${java-short-version}, etc. Ralph On Sep 18, 2014, at 9:51 AM, Gary Gregory wrote: > > I would like the start of my logs to start with

Logging the Java version

2014-09-18 Thread Gary Gregory
I would like the start of my logs to start with the same information "java -version" provides. On the console, "java -version" says: java version "1.8.0_20" Java(TM) SE Runtime Environment (build 1.8.0_20-b26) Java HotSpot(TM) 64-Bit Server VM (build 25.20-b23, mixed mode) I cook this up manuall