svn commit: r923065 - /tomcat/tc5.5.x/trunk/STATUS.txt

2010-03-14 Thread kkolinko
Author: kkolinko Date: Mon Mar 15 05:57:22 2010 New Revision: 923065 URL: http://svn.apache.org/viewvc?rev=923065&view=rev Log: revoke my proposal and add veto to markt's Modified: tomcat/tc5.5.x/trunk/STATUS.txt Modified: tomcat/tc5.5.x/trunk/STATUS.txt URL: http://svn.apache.org/viewvc/to

svn commit: r923063 - /tomcat/tc6.0.x/trunk/STATUS.txt

2010-03-14 Thread kkolinko
Author: kkolinko Date: Mon Mar 15 05:52:48 2010 New Revision: 923063 URL: http://svn.apache.org/viewvc?rev=923063&view=rev Log: Revoke one proposal, and propose another to fix BZ 48903 Modified: tomcat/tc6.0.x/trunk/STATUS.txt Modified: tomcat/tc6.0.x/trunk/STATUS.txt URL: http://svn.apache

Bug report for Tomcat Native [2010/03/14]

2010-03-14 Thread bugzilla
+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned

Bug report for Tomcat 7 [2010/03/14]

2010-03-14 Thread bugzilla
+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned

Bug report for Tomcat Connectors [2010/03/14]

2010-03-14 Thread bugzilla
+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned

Bug report for Tomcat 6 [2010/03/14]

2010-03-14 Thread bugzilla
+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned

Bug report for Tomcat 5 [2010/03/14]

2010-03-14 Thread bugzilla
+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned

Bug report for Taglibs [2010/03/14]

2010-03-14 Thread bugzilla
+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned

DO NOT REPLY [Bug 48694] WebappClassLoader deadlock if web application uses it's own classloader

2010-03-14 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=48694 --- Comment #12 from pmones...@gmail.com 2010-03-14 20:58:10 UTC --- yea I guess you are right. The stacktrace is suspicious in the sense that there is no line number here: at org.apache.catalina.loader.WebappClassLoader.findClass(WebappClas

Re: Using JIRA instead STATUS.txt

2010-03-14 Thread Mladen Turk
On 03/14/2010 07:31 PM, Konstantin Kolinko wrote: I am -1. IMHO JIRA can do a better job then status file. The questions you've raised actually show how hard it is to get something out of status. It's a mixture of hundreds of commit messages, references to other commit messages, p.a.o files th

Re: Using JIRA instead STATUS.txt

2010-03-14 Thread Konstantin Kolinko
I am -1. 1. Voting system in a bug tracker has its purpose: prioritizing of issues. http://www.atlassian.com/software/jira/docs/v3.13.2/voterswatchers.html What you are proposing abuses that system. 2. There are all kinds of votes: +1,-1,+0,-0, with and without arbitrary comments. 3. Patches c

Re: Using JIRA instead STATUS.txt

2010-03-14 Thread Mladen Turk
On 03/14/2010 12:06 PM, Rainer Jung wrote: On 14.03.2010 08:07, Mladen Turk wrote: Hi, I would suggest that we use JIRA instead maintaining STATUS.txt files. Each branch can then be a separate component and each status vote JIRA issue classified as either bug, feature, etc... Voting is supporte

Re: Using JIRA instead STATUS.txt

2010-03-14 Thread Rainer Jung
On 14.03.2010 08:07, Mladen Turk wrote: Hi, I would suggest that we use JIRA instead maintaining STATUS.txt files. Each branch can then be a separate component and each status vote JIRA issue classified as either bug, feature, etc... Voting is supported except that one cannot vote for the create

Re: Using JIRA instead STATUS.txt

2010-03-14 Thread Mark Thomas
On 14/03/2010 07:07, Mladen Turk wrote: Hi, I would suggest that we use JIRA instead maintaining STATUS.txt files. Each branch can then be a separate component and each status vote JIRA issue classified as either bug, feature, etc... Voting is supported except that one cannot vote for the create

Re: Using JIRA instead STATUS.txt

2010-03-14 Thread Peter Roßbach
+1 Peter Am 14.03.2010 um 08:07 schrieb Mladen Turk: Hi, I would suggest that we use JIRA instead maintaining STATUS.txt files. Each branch can then be a separate component and each status vote JIRA issue classified as either bug, feature, etc... Voting is supported except that one cannot vot