Just in case you plan to use this script to fetch TC 7 versions:
On 06.12.2011 06:27, xiam...@apache.org wrote:
Modified: geronimo/external/trunk/tomcat-archetype/svn-actions.sh
URL:
issues)
Components: specs
Environment: Any
Reporter: Rainer Jung
Three bugs in the uuencode implementation corrupt the encoded date. See the
following patch:
http://people.apache.org/~rjung/patches/geronimo-javamail_1.4_spec-uuencode-r1147270.patch
The bug
Just in case you wonder what STRICT_SERVLET_COMPLIANCE actually means
for Tomcat: you can find some details under
http://tomcat.apache.org/tomcat-7.0-doc/config/systemprops.html#Specification
Regards,
Rainer
On 15.07.2011 04:19, Kevan Miller wrote:
From time to time I encounter a problem starting a Geronimo server on a Linux
system (I've always seen it on Ubuntu -- but the problem could exist on other
distributions). The server start seems to hang. However, if you're patient,
which I rarely am,
On 15.07.2011 15:56, Rainer Jung wrote:
On 15.07.2011 04:19, Kevan Miller wrote:
From time to time I encounter a problem starting a Geronimo server on a
Linux system (I've always seen it on Ubuntu -- but the problem could exist
on other distributions). The server start seems to hang. However
Just for your information: 5.5.16 was released a couple of weeks ago,
but has some problems with de delivered packaginf of examples app under
windows.
5.5.17 is expected to be cut on friday and voted stable eventually 1-2
weeks later.
Jeff Genender wrote:
Yep...need to update the plan.
When preparing for the test, have a look at the very interesting
cpustat/cputrack. Without this you won't really be able to judge on the
cpu usage. Classical tools like sar/vmstat/prstat easily lead to wrong
results (the amount of work a single strand [hardware thread] is able to
do is not
Hi Jeff,
I just had a short look at the contents of the tomcat zip. A few
comments, but I can not tell, which of these are actually problems. In
general: a lot of the subdirs under geronimo-1.0/var do not exist any more:
- directory geronimo-1.0/deploy/ does not exist any more (was empty
Hi there,
correction to my previous mail:
1) The strange split of all files between the two src archives was a
failure on my side. Actually there are exactly the same files in both zip
and tarball.
2) The problem with chopped off last characters in file names to some
extent still exists, but it
Concerning my mails related to strange behaviour of the release tarballs:
There is an incompatibility between gnu tar and other tars as well as
different versions of gnu tar whenever the name of a file (including path)
is exactly 100 chars long. POSIX allows exactly 100 chars without using
Hi guys,
unfortunately:
-1 (non binding)
Reason:
The tarballs for source and bin are corrupt. They includes files with a
missing last character in their name. I checked md5 of the downloads (OK).
The zip seems OK. Some differences between the archives might be
intentionally, but obviously not
11 matches
Mail list logo
