[
https://issues.apache.org/jira/browse/MTOMCAT-177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicholas Albion updated MTOMCAT-177:
------------------------------------
Attachment: MTOMCAT-177-tomcat6.patch
Note - I've added a MavenSession component to AbstractCatalinaMojo - it would
probably be possible to use wagonManager.getProxy(url.getProtocol()) as done
here:
https://code.google.com/p/maven-external-dependency-plugin/issues/detail?id=15
...I'm not sure if that would be best practice, but it seems to be deprecated:
http://maven.apache.org/ref/3.0.5/maven-compat/apidocs/org/apache/maven/artifact/manager/WagonManager.html
> tomcat7:deploy ignores proxy settings
> -------------------------------------
>
> Key: MTOMCAT-177
> URL: https://issues.apache.org/jira/browse/MTOMCAT-177
> Project: Apache Tomcat Maven Plugin
> Issue Type: Bug
> Components: tomcat7
> Affects Versions: 2.0
> Reporter: Brad Larson
> Assignee: Olivier Lamy (*$^¨%`£)
> Labels: proxy
> Attachments: MTOMCAT-177.patch, MTOMCAT-177-tomcat6.patch
>
>
> Using these settings:
> <groupId>org.apache.tomcat.maven</groupId>
> <artifactId>tomcat7-maven-plugin</artifactId>
> <version>2.0-SNAPSHOT</version>
> When running tomcat7:deploy behind a network proxy (specified in
> ~/.m2/settings.xml), the deploy will fail with a very generic error message.
> Running outside of the proxy (with no proxy settings in ~/.m2/settings.xml)
> works fine.
> The error message is simply "Connection refused", no other details provided.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
