-
Bug
-
Resolution: Unresolved
-
Major
Maven build step put all build variables on command line as properties. This causes problems when special characters are used. This happens often when non-trivial label expressions are used: -Dlabel_exp=w2k8&&x86.
- is related to
-
JENKINS-25416 text parameter with newlines causing the default goal run
-
- Resolved
-
-
JENKINS-31986 OS-related problems with Maven parameters (from job or from build step)
-
- Open
-
-
JENKINS-28790 Sonar database credentials in build console output not masked since LTS version 1.596.3
-
- Resolved
-
[JENKINS-26684] Maven build step fail to launch mvn process when special chars are present in build variables
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Labels | New: lts-candidate |
Labels | Original: lts-candidate | New: 1.596.2-fixed windows |
Passing all build parameters this way is a horrible idea anyway, but it's probably too late to do anything about it.