The following issue has been updated: Updater: Tim Shadel (mailto:[EMAIL PROTECTED]) Date: Fri, 18 Jun 2004 6:45 PM Comment: This patch allows the RepositoryServlet to load the maven-proxy.properties file from a location specified in the web.xml. This has been tested with Tomcat 5.0.26, but has not been tested in the standalone version. It seems to work OK. It also changes the browse settings to include the context path, and display the full path in the title for a friendly browser history. Changes: Attachment changed to tomcat.patch --------------------------------------------------------------------- For a full history of the issue, see:
http://jira.codehaus.org/browse/MAVENPROXY-11?page=history --------------------------------------------------------------------- View the issue: http://jira.codehaus.org/browse/MAVENPROXY-11 Here is an overview of the issue: --------------------------------------------------------------------- Key: MAVENPROXY-11 Summary: Load configuration from webapp setup Type: Improvement Status: Open Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-component-proxy Assignee: Ben Walding Reporter: Tim Shadel Created: Fri, 18 Jun 2004 6:42 PM Updated: Fri, 18 Jun 2004 6:45 PM Description: When using the webapp setup, the RepositoryServlet should load the configuration file. Otherwise it doesn't seem to work. --------------------------------------------------------------------- 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]