The following comment has been added to this issue: Author: Paul Libbrecht Created: Fri, 12 Dec 2003 2:55 PM Body: Agreed, but we need a maven guru here (or to wait for a later version).
One thing that jira doesn't do thus far is to send bug-reports-updates to commons-dev. Bugzilla does. Paul --------------------------------------------------------------------- View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=JELLY-52 Here is an overview of the issue: --------------------------------------------------------------------- Key: JELLY-52 Summary: provide correct bug reporting link on jelly web site! Type: Bug Status: Unassigned Priority: Major Original Estimate: 5 minutes Time Spent: Unknown Remaining: 5 minutes Project: jelly Components: documentation Fix Fors: 1.1-beta-1 Assignee: Reporter: Ralf Hauser Created: Wed, 21 May 2003 10:42 AM Updated: Fri, 12 Dec 2003 2:55 PM Description: the currently available link under "Jakarta Community" lead me to bugzilla: --> http://jakarta.apache.org/site/getinvolved.html, --> http://jakarta.apache.org/site/bugs.html It is not that obvious to look for "Project Documentation" - "Project Info" - "Issue Tracking" I would guess that QA deserves a top-level link? I have also suggested to bugzilla to close Jelly for input --> http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20120 --------------------------------------------------------------------- JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]