-
Improvement
-
Resolution: Fixed
-
Critical
-
None
-
Platform: All, OS: All
In an M2 project, environment MAVEN_OPTS seems to be ignored. That means that
when having some common settings (e.g. -Dhttp.proxyHost) I need to copy those
values into the "MAVEN_OPTS" field for every single project. That causes a
maintenance nightmare.
I've noticed that on Solaris, but I suspect it affects other platforms as well.
- is duplicated by
-
JENKINS-3536 MAVEN_OPTS env variable ignored by maven builds
-
- Closed
-
[JENKINS-2932] maven2 project doesn't pick up environment variable MAVEN_OPTS
Link |
New:
This issue is duplicated by |
Assignee | New: Andrew Bayer [ abayer ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Do node properties solve this for you? (issue 2918)