You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@archiva.apache.org by "Igor Galic (JIRA)" <ji...@codehaus.org> on 2009/07/10 19:13:22 UTC
[jira] Created: (MRM-1214) Web Application Deployment,
Troubleshooting
Web Application Deployment, Troubleshooting
-------------------------------------------
Key: MRM-1214
URL: http://jira.codehaus.org/browse/MRM-1214
Project: Archiva
Issue Type: Improvement
Components: documentation
Affects Versions: 1.x
Reporter: Igor Galic
Attachments: archiva-docs-webapp.patch
Deploying Archiva in Tomcat or any other JSP Container is easy, especially if one is experienced with said container. Troubleshooting a config however is not very easy, as the logging is spread over a multitude of directories and files.
Rather than trying to patch the log4j.xml, I'm opting for adding a hint in the documentation.
--
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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MRM-1214) Web Application Deployment,
Troubleshooting
Posted by "Maria Odea Ching (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maria Odea Ching closed MRM-1214.
---------------------------------
Resolution: Fixed
Thanks for the patch jmcg! I already applied it to trunk -r793260.
> Web Application Deployment, Troubleshooting
> -------------------------------------------
>
> Key: MRM-1214
> URL: http://jira.codehaus.org/browse/MRM-1214
> Project: Archiva
> Issue Type: Improvement
> Components: documentation
> Affects Versions: 1.x
> Reporter: Igor Galic
> Assignee: Maria Odea Ching
> Fix For: 1.2.2
>
> Attachments: archiva-docs-webapp.patch
>
>
> Deploying Archiva in Tomcat or any other JSP Container is easy, especially if one is experienced with said container. Troubleshooting a config however is not very easy, as the logging is spread over a multitude of directories and files.
> Rather than trying to patch the log4j.xml, I'm opting for adding a hint in the documentation.
--
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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MRM-1214) Web Application Deployment,
Troubleshooting
Posted by "Maria Odea Ching (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maria Odea Ching updated MRM-1214:
----------------------------------
Assignee: Maria Odea Ching
Fix Version/s: 1.2.2
> Web Application Deployment, Troubleshooting
> -------------------------------------------
>
> Key: MRM-1214
> URL: http://jira.codehaus.org/browse/MRM-1214
> Project: Archiva
> Issue Type: Improvement
> Components: documentation
> Affects Versions: 1.x
> Reporter: Igor Galic
> Assignee: Maria Odea Ching
> Fix For: 1.2.2
>
> Attachments: archiva-docs-webapp.patch
>
>
> Deploying Archiva in Tomcat or any other JSP Container is easy, especially if one is experienced with said container. Troubleshooting a config however is not very easy, as the logging is spread over a multitude of directories and files.
> Rather than trying to patch the log4j.xml, I'm opting for adding a hint in the documentation.
--
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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira