Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Maven dependencies are download each time the workspace is getting restarted #13603

Closed
slemeur opened this issue Jun 21, 2019 · 7 comments
Closed
Assignees
Labels
kind/bug Outline of a bug - must adhere to the bug report template. severity/P1 Has a major impact to usage or development of the system.

Comments

@slemeur
Copy link
Contributor

slemeur commented Jun 21, 2019

Description

Start a workspace, wait for dependencies to be loaded, stop the workspace and restart it.

  • Dependencies are reloaded by the Java LS

Reproduction Steps

Start a workspace, wait for dependencies to be loaded, stop the workspace and restart it.

  • Dependencies are reloaded by the Java LS

OS and version:
Che 7 RC 2

@slemeur slemeur added kind/bug Outline of a bug - must adhere to the bug report template. severity/P1 Has a major impact to usage or development of the system. team/languages labels Jun 21, 2019
@sleshchenko
Copy link
Member

If you type mvn clean install in maven container - then dependencies will be downloaded after each restart of workspace, and it iis 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

As about Java LS - it may be caused by the same issue OR volume for storing resolved dependencies may be missed @tolusha Can you comment?

@tsmaeder tsmaeder mentioned this issue Sep 10, 2019
41 tasks
@tsmaeder
Copy link
Contributor

The devfile here does not contain a persistent volume for ~/.m2. Need to mount the "m2" volume to the java plugin home dir.

@tsmaeder
Copy link
Contributor

Let's also check all other devfiles and fix as appropriate.

@amisevsk
Copy link
Contributor

@tsmaeder Is this something that should be fixed in the devfiles or in the plugin meta.yaml itself?

@tsmaeder
Copy link
Contributor

Blocked by #14634

@tsmaeder tsmaeder added the status/blocked Issue that can’t be moved forward. Must include a comment on the reason for the blockage. label Sep 24, 2019
@tsmaeder tsmaeder mentioned this issue Sep 24, 2019
30 tasks
@tsmaeder tsmaeder removed the status/blocked Issue that can’t be moved forward. Must include a comment on the reason for the blockage. label Oct 2, 2019
@tsmaeder
Copy link
Contributor

tsmaeder commented Oct 2, 2019

I think it makes sense to mount the volume in the plugin meta.yml, becuase we want this for all java tooling sidecars.

@tsmaeder
Copy link
Contributor

tsmaeder commented Oct 2, 2019

@svor as a first step, let's put this into the 0.50 version of the Java plugins when you create it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Outline of a bug - must adhere to the bug report template. severity/P1 Has a major impact to usage or development of the system.
Projects
None yet
Development

No branches or pull requests

5 participants