[
https://issues.apache.org/jira/browse/SHINDIG-718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12657453#action_12657453
]
Chico Charlesworth commented on SHINDIG-718:
--------------------------------------------
I replaced fix-proxy-bug.patch with the latest patch (i.e.
fix-718-727075-bug.patch), which works with the current revision of shindig.
The maven plugins have been updated already, so the only problem at the moment
is the proxy provider.
Currently the issue is that guice injects a default Proxy, even though the
Inject annotation is set to be optional (i.e. @Inject(optional=true)), when it
should be set to null. See issue
http://code.google.com/p/google-guice/issues/detail?id=107 for more details.
IMHO this might end up causing problems not only when running tests, but also
when running shindig in production behind a proxy as the BasicHttpFetcher will
at the moment always ignore those proxy settings.
> 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.
