Skip to content
This repository has been archived by the owner on Dec 18, 2021. It is now read-only.

Configurable maven install directory #17

Closed
dantran opened this issue Dec 16, 2015 · 9 comments
Closed

Configurable maven install directory #17

dantran opened this issue Dec 16, 2015 · 9 comments

Comments

@dantran
Copy link

dantran commented Dec 16, 2015

My CI env does not allow the build to use its home directory, and maven wrapper is current unpack maven under ~/.m2

@jvanzyl
Copy link

jvanzyl commented Feb 11, 2016

Where would you like it and how would you like to specify it?

@dantran
Copy link
Author

dantran commented Feb 11, 2016

we have a conventions to cache this kind of artifacts under top parent's .external-resources.

at jenkins top level parent directory is ${WORKSPACE}

@jvanzyl
Copy link

jvanzyl commented Feb 11, 2016

Yes, but how would you specify this so that the wrapper understands. An envar?

@dantran
Copy link
Author

dantran commented Feb 11, 2016

env var sounds reasonable.

@ppalaga
Copy link

ppalaga commented Mar 7, 2017

-Dmaven.user.home=$myDir is undocumented but works already. Note that the current impl. is a bit picky about the order of command line args: it likes getting sysprops first.

@mosabua
Copy link
Member

mosabua commented Sep 12, 2017

we now have an env var called MVNW_VERBOSE... if you want to do something similar for the install feel free to send a PR @dantran ;-)

@TylerLu
Copy link

TylerLu commented Oct 25, 2018

I scrutinized the source code and solved this by setting the MAVEN_USER_HOME environment variable. I am working on Azure:
set MAVEN_USER_HOME=D:\home\site\deployments\tools\maven

@mosabua
Copy link
Member

mosabua commented Dec 18, 2018

I added this to the README docs now.

@mosabua mosabua closed this as completed Dec 18, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
5 participants