-
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
-
Code changed in jenkins
User: Oliver Gondža
Path:
core/src/main/java/hudson/tasks/Maven.java
test/src/test/java/hudson/tasks/MavenTest.java
http://jenkins-ci.org/commit/jenkins/66b62b9a1f9b68ef5e61304c6aff6e1bef37514e
Log:
Merge pull request #1567 from olivergondza/maven-special-chars-dirty
JENKINS-26684 Escape special chars in maven build step arguments