Which docker image to use for Java projects based on Maven?March 14, 2019 at 2:50pm
Which theiaide/theia-java docker image can I use to test a standard theia? I tried version 'next' -> is corrupted when switching the workspace, version 'latest' -> does not recognize my java project (I used Maven).
I got the version 'theiaide/theia-full:latest" running.
The theiaide/theia-full version recognizes my Java project but my external dependencies are not found. What should I do?
Maven is also not in the path. Is it not installed?
March 14, 2019 at 6:42pm
March 15, 2019 at 7:23am
March 18, 2019 at 12:22pm
March 19, 2019 at 3:17pm
March 21, 2019 at 7:04am
I built the docker image from your pull request and now the Maven command is available and also the classes are found in the classpath.
One question is: I use maven dependencies from my own intranet maven repository and I am behind a network proxy. Where do I tell Theia to use my proxy and where to say which domain names should be ignored by the proxy? I could get the maven dependencies only to be found after I manually built my project with the terminal an my settings.xml file to set the proxy.
March 21, 2019 at 2:49pm
I am not sure if this is a Theia or a docker/ubuntu question. I guess you have setup docker on your host to use the proxy, or else you might have had difficulty to build the theia-java image.
From what I observe, setting-up the proxy for docker on the host, is the only proxy setting I need, behind my own corporate proxy, so that Theia images can run and use resources from the internet. I assume docker does some magic to make that happen...
So maybe try to set your Maven server or internal domain(s) as an exclusions, as part of your host docker proxy config? On my Ubuntu 16.04 laptop, I did it I think in /etc/docker/daemon.json.
something in the form:
export http_proxy="http://<host>:<port>" export https_proxy="http://<host>:<port>" export no_proxy="<excluded domain1>, <excluded domain2>, <excluded domain3>"
... and restart your docker service
You may need to try different things...
Maybe you can try the "Configure the Docker client" if applicable