All,
I opened this thread for general comments and questions about the
release. Let's have the discussions here and leave the vote thread
for +/- voting only so it will be easier to process
Thanks.
Matt Hogstrom
[EMAIL PROTECTED]
On Dec 18, 2006, at 9:49 AM, Kevan Miller wrote:
There's a source file missing a license header. Not sure if it was
added after my last scan of the code or if I just missed it.
Anyway, it needs to be fixed.
All servers start. I'm getting some [info] log messages sent to
STDOUT, but I
anita,
If I turn logging up to INFO in var/log/server-log4j.properties I get
information in the log.
On Dec 18, 2006, at 10:37 AM, Matt Hogstrom wrote:
All,
I opened this thread for general comments and questions about the
release. Let's have the discussions here and leave the vote
On Dec 18, 2006, at 10:46 AM, Matt Hogstrom wrote:
On Dec 18, 2006, at 9:49 AM, Kevan Miller wrote:
There's a source file missing a license header. Not sure if it was
added after my last scan of the code or if I just missed it.
Anyway, it needs to be fixed.
All servers start. I'm
Matt,
I had to change the following lines in server-log4j.properties to
get system information logged:
log4j.rootLogger=INFO, CONSOLE, FILE
log4j.appender.FILE.Threshold=INFO
In addition I see the following stack trace during shutdown. A fix
for this is already available in rev 488106:
I think its a preference. At this point I think M1 is what it is and
we'll update the Wiki with known issues.
On Dec 18, 2006, at 12:49 PM, anita kulshreshtha wrote:
Matt,
I had to change the following lines in server-log4j.properties to
get system information logged:
Thanks for finding this Kevan.
I reposted the source, there are no modules.
Updated source is in:
http://people.apache.org/~hogstrom/2.0-M1/
Thanks for finding this.
On Dec 18, 2006, at 12:36 PM, Kevan Miller wrote:
On Dec 18, 2006, at 10:46 AM, Matt Hogstrom wrote:
On Dec 18, 2006, at
Rerouting to this thread from [VOTE] 2.0-M1 Release
Hi All,
I have two basic comments/questions.
1- I see a bunch of INFO messages in both Tomcat and Jetty at startup, not a
show stopper for this release.
2- Deployment on Jetty is not behaving exactly as I expected. Not sure if I
messed up