[
https://issues.apache.org/jira/browse/SHINDIG-718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12657446#action_12657446
]
Henning Schmiedehausen commented on SHINDIG-718:
------------------------------------------------
Wouldn't this patch break functionality for people needing to set this and
expecting it to be done by Guice? I have a bad feeling changing something that
IMHO makes perfect sense so that developer tests pass in a limited environment.
Fixing up the proxy usage in the Fetcher might be more beneficial in the long
run. I agree that updating to newer maven plugins makes sense. Where BTW did
fix-proxy-bug.patch go?
> Building shindig from behind a proxy fails
> ------------------------------------------
>
> Key: SHINDIG-718
> URL: https://issues.apache.org/jira/browse/SHINDIG-718
> Project: Shindig
> Issue Type: Bug
> Components: Common Components (Java)
> Environment: Behind a proxy
> Reporter: Chico Charlesworth
> Attachments: fix-718-727075-bug.patch
>
>
> When the maven build runs behind a proxy the test
> EndToEndTest.testTemplates() fails.
> i.e. mvn clean install -Dhttp.proxyHost=<host> -Dhttp.proxyPort=<port>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
