Op donderdag, 16 juni 2011 18:55 schreef Christopher Schultz
ch...@christopherschultz.net:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ronald,
On 6/16/2011 11:40 AM, Ronald Klop wrote:
I created a release package. First had to find a computer with Windows,
because it
2011/6/17 Ronald Klop ronald-mailingl...@base.nl:
Regarding 'wine'. (...)
Darn, I look closer now and see the 'unless=skip.installer' in dist.xml.
Wine is required to build the exe installer.
This step can be turned off, as you have found.
Thanks, I'm very close to debugging Tomcat myself. Is
A little lobby is started:
http://marc.info/?l=tomcat-devm=130805807619349w=2
Thanks, but no reply yet from jfclere. He must be busy.
I'm not familiar with the inner workings of the Tomcat organization, but
shouldn't releases be less dependent on one person?
Ronald.
Op dinsdag, 14 juni 2011
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ronald,
On 6/16/2011 6:39 AM, Ronald Klop wrote:
A little lobby is started:
http://marc.info/?l=tomcat-devm=130805807619349w=2
Thanks, but no reply yet from jfclere. He must be busy.
I'm not familiar with the inner workings of the Tomcat
Good tip.
I created a release package. First had to find a computer with Windows, because
it needs wine (I didn't want to learn wine on FreeBSD today), but ok it builds
now.
Now I'll wait for my precious bug fix to get committed to 6. :-)
Ronald.
Op donderdag, 16 juni 2011 16:54 schreef
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ronald,
On 6/16/2011 11:40 AM, Ronald Klop wrote:
I created a release package. First had to find a computer with Windows,
because it needs wine (I didn't want to learn wine on FreeBSD today),
but ok it builds now.
Wait, what? Why do you need
Hi,
I see the issue if solved in an upcoming version of Tomcat. Thank you very much
for that. But can I expect an upcoming version of Tomcat 6.0 in the not too
distant future?
At the tomcat-dev list I only see recent votings for 7.0.x.
Who normally is the initiator of the 6.x release cycle?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ronald,
On 6/14/2011 6:23 AM, Ronald Klop wrote:
I see the issue if solved in an upcoming version of Tomcat. Thank you
very much for that. But can I expect an upcoming version of Tomcat 6.0
in the not too distant future?
At the tomcat-dev list I
Hi,
I'm running a 4 node cluster and seeing the same exception as described in
this issue.
https://issues.apache.org/bugzilla/show_bug.cgi?id=51306
What can I do to workaround it or what can I information can I provide to help?
I'm running 6.0.32 with a securitymanager on Debian 5. Java
