.m2 dependencies are getting stored in a '?' folder in the project

[slemeur]

Description

.m2 dependencies are getting stored in a '?' folder in the project which looks extremely odd and trigger more the attention about a bug than anything else..

Reproduction Steps

• Create a workspace based on the stack java-maven
• import https://github.com/spring-projects/spring-petclinic
• open a terminal and run the command ./mvnw spring-boot:run

OS and version:
Che 7 RC 2

[slemeur]

And then build is failing because of this error

[ERROR] Unknown lifecycle phase "/home/user/.m2". You must specify a valid lifecycle phase or a goal in the format <plugin-prefix>:<goal> or <plugin-group-id>:<plugin-artifact-id>[:<plugin-version>]:<goal>. Available lifecycle phases are: validate, initialize, generate-sources, process-sources, generate-resources, process-resources, compile, process-classes, generate-test-sources, process-test-sources, generate-test-resources, process-test-resources, test-compile, process-test-classes, test, prepare-package, package, pre-integration-test, integration-test, post-integration-test, verify, install, deploy, pre-clean, clean, post-clean, pre-site, site, post-site, site-deploy. -> [Help 1]

[slemeur]

cc @tsmaeder

[sleshchenko]

It is caused by lack of user information in /etc/passwd, to fix it it is needed to build custom image and make maven container - openshift compatible where /etc/passwd will be writable and entrypoint will fill in user name if needed. More see #13561

[tsmaeder]

@sleshchenko I suspec this is fixed now?

[amisevsk]

This issue is resolved for our patched base images; the /etc/passwd issue is still present for community images, but that is a larger issue (most community images will not work with Che), so I think this issue can be closed.