Bug 474491 - Maven 2 (legacy) Plugin does not resolve MAVEN_OPTS when JVM-parameters are set
Summary: Maven 2 (legacy) Plugin does not resolve MAVEN_OPTS when JVM-parameters are set
Status: NEW
Alias: None
Product: Hudson
Classification: Technology
Component: Plugins (show other bugs)
Version: 3.3.0   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Winston Prakash CLA
QA Contact: Geoff Waymark CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-08-07 07:08 EDT by Thomas Baldauf CLA
Modified: 2015-08-07 07:08 EDT (History)
4 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Baldauf CLA 2015-08-07 07:08:42 EDT 
Running a job with a Maven 2 (legacy) build step and JVM-parameters, since Hudson 3.3.0 the following error message appears in the log:

Error: Could not find or load main class MAVEN_OPTS

This is because Hudson or the Maven 2 plugin apparently does not resolve the variabe correctly but uses the strin "MAVEN_OPTS" itself, adding the JVM-parameters as in the following example command line:

"<java_home>\java.exe" MAVEN_OPTS -Xmx2048m -XX:PermSize=512m -Dspring.profiles.active=test ... clean deploy

This is not happening when there are no JVM-parameters in the job config.