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=23461>. 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=23461 "Memory leak" in xpath evaluations ------- Additional Comments From [EMAIL PROTECTED] 2004-10-21 14:23 ------- Tracking of bugs and issues has moved from bugzilla to Jira. See the Jira home page at http://nagoya.apache.org/jira/ Everyone is free to view public issues there, but if you want to create a bug or an issue, or comment on one you will need a Jira account. Before you create a new Jira account you should check if one hasn't already been created for you. In the migration from Bugzilla to Jira, people who had previously created or updated Bugzilla bugs had Jira accounts created for them automatically - the new Jira Username would be the same as the Bugzilla Username. So you should first enter your Userid in the Jira login panel and click the "Forgot Password" link to get the password that Jira has set for this new account e-mailed to you. Otherwise you will need to create a Jira account. To find a migrated issue, including this one, the JIRA home page has a text field in which you can enter the old Bugzilla number and go straight to the Jira issue. For XalanJ2 the issue keys are of the form XALANJ-##### where ##### is a number, but not related to the old Bugzilla number. In this particular case, the new Jira issue is XALANJ-1673. You can get to it directly from http://issues.apache.org/jira/browse/XALANJ-1673. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
