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

uber -j fails with "Invalid cross-device link" #290

Closed
wagjo opened this issue Sep 15, 2015 · 6 comments
Closed

uber -j fails with "Invalid cross-device link" #290

wagjo opened this issue Sep 15, 2015 · 6 comments

Comments

@wagjo
Copy link
Contributor

wagjo commented Sep 15, 2015

My .m2 directory is on another device. When running boot pom uber -j, it fails with "Invalid cross-device link".

Workaround is to place .m2 repo in the same device as .boot

@alandipert
Copy link
Contributor

Note: BOOT_LOCAL_REPO controls .m2 cache location.

@Deraen
Copy link
Member

Deraen commented Sep 15, 2015

And BOOT_HOME the location of .boot directory, either could be changed to reside on the same disk as the other.

@martinklepsch
Copy link
Member

Can we close this or is there something that should be done?

@wagjo
Copy link
Contributor Author

wagjo commented Oct 25, 2015

Please do not close this as the bug is still present. AFAIK you can fix this issue by not using hard links in your .boot cache.

@wagjo
Copy link
Contributor Author

wagjo commented Oct 25, 2015

... or you can explicitly say in the documentation that both .boot and .m2 must reside in the same physical device.

@micha
Copy link
Contributor

micha commented Oct 25, 2015

Oh, sorry about that. I was looking at the nio APIs to detect this condition, I think it can be done.

@micha micha closed this as completed in efaaaae Dec 19, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants