[ https://issues.jboss.org/browse/FORGE-421?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III commented on FORGE-421: ------------------------------------------ Hi, We currently don't support Proxy configuration, but it's definitely something we need! Is this something you could look at? It's relatively simple, I think. Just need to set some system properties: http://docs.oracle.com/javase/6/docs/technotes/guides/net/proxies.html this could be done by setting FORGE_OPTS in your terminal environment before executing Forge itself (or adding them to your profile or windows settings): unix: {code}export FORGE_OPTS="-Dhttp.proxyHost=webcache.mydomain.com -Dhttp.proxyPort=8080"{code} windows: {code}set FORGE_OPTS="-Dhttp.proxyHost=webcache.mydomain.com -Dhttp.proxyPort=8080"{code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/FORGE-421?page=com.atlassian.jira.plugin.... ] Esteve Aviles commented on FORGE-421: ------------------------------------- Hi, I tried setting FORGE_OPTS and running forge + proxy params in the CLI with the same result as before. I also tried with https.proxy* params without succeed. Regards -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/FORGE-421?page=com.atlassian.jira.plugin.... ] Ivan St. Ivanov commented on FORGE-421: --------------------------------------- Hi guys, I am not a proxy expert. However, I browsed through the forge code and found that it is using JGit to download plugins from Github (as it is the case with Arquillian). I then browsed JGit's code and found that it supports proxies and as far as I got it, it uses the proxy selector mechanism described in the document linked by Lincoln. To be more precise: it uses the default proxy selector. Which happens to use exactly these system properties that you set. I saw a suggestion in the document that if you are on Windows or Gnome 2.x, you can edit your <JRE-dir>/lib/net.properties file and make the default proxy selector use your system proxy. Furthermore, you can try to uncomment the lines in the same file (no matter what OS you are using, just keep the useSystemProxies to false) that configure the HTTP proxy. And then run forge again. Tomorrow I will try this at work as well. Cheers, Ivan -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/FORGE-421?page=com.atlassian.jira.plugin.... ] Esteve Aviles commented on FORGE-421: ------------------------------------- Hi, I have tried what Ivan says with this result: [tcapplet] tcapplet $ forge install-plugin arquillian Connecting to remote repository [https://raw.github.com/forge/plugin-repository/master/repository.yaml]... ***ERROR*** [forge install-plugin] Malformed reply from SOCKS server Regards -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/FORGE-421?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III commented on FORGE-421: ------------------------------------------ Hey Ivan, I'm not sure if you can increase logging, but we don't have any explicit support for proxies at the moment. Are you looking for something to pick up? This could be a good issue for you since you can actually reproduce the problem. What do you think? It would really help us out a lot! ~Lincoln -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/FORGE-421?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III reassigned FORGE-421: ---------------------------------------- Assignee: Ivan St. Ivanov Hey Ivan! I've assigned this issue and given you permissions for future ones as well :) Sorry about that! In order to get more information, you might have to Debug Forge like so: https://docs.jboss.org/author/display/FORGE/Debugging+Forge Does that help? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/FORGE-421?page=com.atlassian.jira.plugin.... ] Ivan St. Ivanov commented on FORGE-421: --------------------------------------- Hi guys, I have a question. Right now I found a way to setup programatically Apache HTTP client and JGit to work with a proxy. And this is done with just Forge instruments (no additional manual steps than configuring Forge). However, I just found that if you want to use maven behind a proxy (and Forge uses it for building the just downloaded plugin), then you have to change your settings.xml (http://maven.apache.org/guides/mini/guide-proxies.html). So, I had the following dilemma: maybe we should tell the forge users behind proxies that they should setup their settings.xml so that Forge can access external Maven repos? Argh, this sounds nasty: I hate manual configurations done by users!!! However, when given a second thought: you are behind a proxy... And you want to use open source software, that is most likely not located on your enterprise maven repository. Then you should definitely setup your settings.xml to access external sites! Otherwise you can live just with what you find on your www.proprietary.com intranet... Do you think the same or I miss something? Can we rely on the fact that Forge users that want to use our tool from within corporate environments have already setup their settings.xml to use their company proxy? Cheers, Ivan -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/FORGE-421?page=com.atlassian.jira.plugin.... ] Ivan St. Ivanov commented on FORGE-421: --------------------------------------- Hey Lincoln, How was your vacation? Did you drink plenty of Alt and Kolsch? :-) I also tried to exploit the Forge capabilities for configuring Maven. However, besides passing some parameters, like for example system properties, on the command line, I did find anything else. And to enable proxies in Maven, you need to touch settings.xml. Or at least this is what all the resources I found say (I actually tried some proposals for adapting MAVEN_OPTS, but they did not work). What I can do is download Maven source code and look there what exactly happens. Or maybe you can point me to the Forge code that manipulates Maven, as maybe I have missed something? Cheers, Ivan -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/FORGE-421?page=com.atlassian.jira.plugin.... ] Ivan St. Ivanov commented on FORGE-421: --------------------------------------- Hi Lincoln, Thanks for the idea of using the Maven Container! However, I'm not yet sure that the MavenContainer instance has any impact on the executeMaven method, that is eventually run upon building the plugin. As for the username/password support - thanks for reminding me! I thought of adding them, but then I forgot. It will not be a big deal... However, I'm afraid I will not be able to test it, because my company proxy does not use such stuff. Thanks also for merging my changes! They seem to be all there, even an experiment that I did some time ago and was not supposed to go into the upstream (it works, though). I am still afraid of using Git :-) BTW, something off topic. Do you have a good resource on how should we use Git when working with a Github project? I use mainly this: https://community.jboss.org/wiki/ArquillianDevelopmentAndContribution However, it does not answer an important question: how do I keep my origin repository (ivannov/core) up-to-date with the upstream one (forge/core). I tried to do that by pushing to ivannov/core after I pull from forge/core, but you saw what a mess I produced with that approach... Thanks, Ivan -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/FORGE-421?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III commented on FORGE-421: ------------------------------------------ Awesome! Regarding your last question - this might help: https://docs.jboss.org/author/display/FORGE/Contribute+or+Get+Involved -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/FORGE-421?page=com.atlassian.jira.plugin.... ] Esteve Aviles commented on FORGE-421: ------------------------------------- Hi, No luck. I've tried the solution but errors still persist. I am using the last version: JBoss Forge, version [ 1.0.2.Final ] - JBoss, by Red Hat, Inc. [ http://jboss.org/forge ] The error is as follows: Connecting to remote repository [https://raw.github.com/forge/plugin-repository/master/repository.yaml]... ***ERROR*** [forge install-plugin] Connection to https://raw.github.com refused Can I get more stacktrace to upload? Regards -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/FORGE-421?page=com.atlassian.jira.plugin.... ] Esteve Aviles commented on FORGE-421: ------------------------------------- Lincoln, Opened FORGE-539 Don't worry. Just trying to contribute. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira