Compilation - Behind Proxy

Flow
1

Hi

I’m new to Vaadin and decided to start with version 10. I downloaded the spring project from Vaadin Start then run it in eclipse.
Viewed it in Firefox looks ok but in IE its not. I’ll be making an app that need to support IE. I read that it is supported by 10
once you compile to production mode and so I did compiled it (based on https://vaadin.com/docs/v10/flow/production/tutorial-production-mode-basic.html ).
I was able to dowload other libraries behind a proxy with no problem however I have some trouble with compilation. Here are some errors/warnings I got:

[WARNING]
Could not transfer metadata org.webjars.bowergithub.vaadin:vaadin-material-styles/maven-metadata.xml from/to Vaadin Directory (http://maven.vaadin.com/vaadin-addons): connect timed out
[WARNING]
Could not transfer metadata org.webjars.bowergithub.vaadin:vaadin-material-styles/maven-metadata.xml from/to central (https://repo.maven.apache.org/maven2): connect timed out
[WARNING]
Could not transfer metadata org.webjars.bowergithub.vaadin:vaadin-material-styles/maven-metadata.xml from/to vaadin-snapshots (https://oss.sonatype.org/content/repositories/vaadin-snapshots/): connect timed out
[WARNING]
Could not transfer metadata org.webjars.bowergithub.vaadin:vaadin-material-styles/maven-metadata.xml from/to vaadin-prereleases (https://maven.vaadin.com/vaadin-prereleases): connect timed out
[WARNING]
Could not transfer metadata org.webjars.bowergithub.vaadin:vaadin-material-styles/maven-metadata.xml from/to vaadin-snapshot (https://oss.sonatype.org/content/repositories/vaadin-snapshots/): connect timed out
[WARNING]
Failure to transfer org.webjars.bowergithub.vaadin:vaadin-material-styles/maven-metadata.xml from http://maven.vaadin.com/vaadin-addons was cached in the local repository, resolution will not be reattempted until the update interval of Vaadin Directory has elapsed or updates are forced. Original error: Could not transfer metadata org.webjars.bowergithub.vaadin:vaadin-material-styles/maven-metadata.xml from/to Vaadin Directory (http://maven.vaadin.com/vaadin-addons): connect timed out
[WARNING]
Failure to transfer org.webjars.bowergithub.vaadin:vaadin-material-styles/maven-metadata.xml from https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced. Original error: Could not transfer metadata org.webjars.bowergithub.vaadin:vaadin-material-styles/maven-metadata.xml from/to central (https://repo.maven.apache.org/maven2): connect timed out
[WARNING]
Failure to transfer org.webjars.bowergithub.vaadin:vaadin-material-styles/maven-metadata.xml from https://oss.sonatype.org/content/repositories/vaadin-snapshots/ was cached in the local repository, resolution will not be reattempted until the update interval of vaadin-snapshots has elapsed or updates are forced. Original error: Could not transfer metadata org.webjars.bowergithub.vaadin:vaadin-material-styles/maven-metadata.xml from/to vaadin-snapshots (https://oss.sonatype.org/content/repositories/vaadin-snapshots/): connect timed out
[WARNING]
Failure to transfer org.webjars.bowergithub.vaadin:vaadin-material-styles/maven-metadata.xml from https://maven.vaadin.com/vaadin-prereleases was cached in the local repository, resolution will not be reattempted until the update interval of vaadin-prereleases has elapsed or updates are forced. Original error: Could not transfer metadata org.webjars.bowergithub.vaadin:vaadin-material-styles/maven-metadata.xml from/to vaadin-prereleases (https://maven.vaadin.com/vaadin-prereleases): connect timed out
[WARNING]
Failure to transfer org.webjars.bowergithub.vaadin:vaadin-material-styles/maven-metadata.xml from https://oss.sonatype.org/content/repositories/vaadin-snapshots/ was cached in the local repository, resolution will not be reattempted until the update interval of vaadin-snapshot has elapsed or updates are forced. Original error: Could not transfer metadata org.webjars.bowergithub.vaadin:vaadin-material-styles/maven-metadata.xml from/to vaadin-snapshot (https://oss.sonatype.org/content/repositories/vaadin-snapshots/): connect timed out
…
[INFO]
Installing node version v8.11.1
[INFO]
Downloading https://nodejs.org/dist/v8.11.1/win-x86/node.exe to C:\Users\a012001566\eclipse-workspace\my-web-app\target\cache\node-v8.11.1-win-x86.exe
[INFO]
No proxies configured

I have defined proxy in settings.xml. That is why I know its working because I was able to download and run the poject. I tried compiling
it using eclipse and directly from maven via commandline. I tried running maven with update and even tried nuking my m2 repository. I tried
running maven with proxy parameters.

Any ideas what causing this?

2

is your configuration similar to this?

<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0
                  https://maven.apache.org/xsd/settings-1.0.0.xsd">
  ...
<proxies>
<proxy>
  <id>myproxy</id>
  <active>true</active>
  <protocol>http</protocol>
  <host>proxy.somewhere.com</host>
  <port>8080</port>
  <username>proxyuser</username>
  <password>somepassword</password>
  <nonProxyHosts>*.google.com|ibiblio.org</nonProxyHosts>
</proxy>
3

Diego Sanz Villafruela:
is your configuration similar to this?

<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0
                  https://maven.apache.org/xsd/settings-1.0.0.xsd">
  ...
<proxies>
<proxy>
  <id>myproxy</id>
  <active>true</active>
  <protocol>http</protocol>
  <host>proxy.somewhere.com</host>
  <port>8080</port>
  <username>proxyuser</username>
  <password>somepassword</password>
  <nonProxyHosts>*.google.com|ibiblio.org</nonProxyHosts>
</proxy>

Yes, my configuration looks extactly like that. I configured to use it as well. Was able to download other libraries so I know its working. But for those libraries mentioned it failed. But if you access it in browser its there.