Paul et al, We James developers have discovered an issue with logging and Phoenix 4.0 release build. Specifically, when we use the Phoenix 4.0 beta release, all of our logging works great. Log entries all go to the correct targets and whatnot. However, after the upgrade to the Phoenix 4.0 release, all logs go to the default logger's log file. This is obviously a big problem for us.
My first question is, is this a known issue with Phoenix 4.0? Has anyone else seen it? My second question is, if so, is it resolved in Phoenix 4.0.1? Any help would be greatly appreciated. Thanks. --Peter > -----Original Message----- > From: Paul Hammant [mailto:[EMAIL PROTECTED] > Sent: Wednesday, October 09, 2002 2:27 PM > To: Avalon-Phoenix Developers List > Cc: Avalon Applications Developers List > Subject: Phoenix 4.0.1 preview release > > Folks, > > > http://jakarta.apache.org/builds/jakarta-avalon-phoenix/nightly/2002-10- > 09/ > > It includes .. > > * better logging and backwards compatability > * An updated MX4J (actually from their CVS HEAD) with serious bugs fixed. > * Actual delete of the contents of the work/ directory on start. > * Wrapper 2.2.8 (Windows only) for thunking into the Windows services > panel. > > This is compatible with all the usual SAR files including the incredibly > exiting Catalina SAR (Sevak-Catalina from Daniel K). > > When the MX4J team release 1.1.1, we'll do the same for 4.0.1 formally. > This URL is for those that want to see the changes now and can't wait a > few days. > > I've not uploaded the source as the build.xml will try to get the MX4J > 1.1 release which is no longer compatible. I have also not committed > the changed build.xml for the same reason, unless people are willing to > make some manual jar replacements after the 'get-mx4j' target. > > Maybe if we can be brave with the inclusion of the MX4J jars, I could > date suffix them as we do with other jars. We don't as we are unsure > that the MX4J project is correctly licensing the javax.management > classes. At least that is why I think we are not uploading the jars to > CVS.... > > Regards, > > - Paul > > > -- > To unsubscribe, e-mail: <mailto:avalon-apps-dev- > [EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:avalon-apps-dev- > [EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
