You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2006/04/20 09:46:42 UTC

DO NOT REPLY [Bug 37302] - Custom context loader unable to find Tomcat jar files

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=37302>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=37302





------- Additional Comments From michaelpub@gmail.com  2006-04-20 07:46 -------
We too had this problem and I spent a few days trying to figure it out.  We have
one project using 5.5.9 and it worked fine.  So we used their same environment
but with Tomcat 5.5.16 and was having problems.  I ended up downloading all the
tomcat versions from 5.5.9 to 5.5.17 to find out what was causing the problem.

When going form 5.5.x to 5.5.y, one would expect minor changes and bug fixes
only.  Perhaps it's just a confusion about the versioning system, but I believe
such a minor increment should not have regression issues.

I vote to add the rule back, and to make the change for the next major version,
5.6 or 6.0 or whatever.  I could understand if the rule was removed because it
was causing problems, but to remove it simply because it was thought to be
useless is a bit careless, especially now with evidence to the contrary.

-Michael

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org