DO NOT REPLY [Bug 33117] Deep link into Bugzilla broken on ROOT/index.jsp

2010-03-13 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=33117 rodriguez...@aol.com changed: What|Removed |Added Status|CLOSED |RESOLVED -- Configure bugma

DO NOT REPLY [Bug 33117] Deep link into Bugzilla broken on ROOT/index.jsp

2010-03-13 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=33117 Konstantin Kolinko changed: What|Removed |Added Status|RESOLVED|CLOSED -- Configure bugmail:

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

2010-03-13 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=48694 --- Comment #11 from aullr...@blackducksoftware.com 2010-03-13 15:44:31 UTC --- Can't see how you'd get into this situation with the current source code. The stack traces indicate that findClass on the WebappClassLoader would have to be a sy

DO NOT REPLY [Bug 48903] ClassLoader deadlock when compiling JSP pages in 6.0.26

2010-03-13 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=48903 --- Comment #3 from Konstantin Kolinko 2010-03-14 00:31:00 UTC --- Created an attachment (id=25125) --> (https://issues.apache.org/bugzilla/attachment.cgi?id=25125) MyClassLoader.java - sample of reflectively calling JDK7 API I just test

DO NOT REPLY [Bug 48906] New: Client's context information is not updated automatically in conf/Catalina

2010-03-13 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=48906 Summary: Client's context information is not updated automatically in conf/Catalina Product: Tomcat 6 Version: 6.0.26 Platform: PC OS/Version: other Status: N

DO NOT REPLY [Bug 48906] Client's context information is not updated automatically in conf/Catalina

2010-03-13 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=48906 Konstantin Kolinko changed: What|Removed |Added Status|NEW |RESOLVED Resolution|

Using JIRA instead STATUS.txt

2010-03-13 Thread 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 vote for the created issue, so that would be presumed. Howev