Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 353157

Summary:	Ability to fork jetty:run
Product:	[RT] Jetty	Reporter:	Gili Mising name <cowwoc2020>
Component:	other	Assignee:	Jan Bartel <janb>
Status:	RESOLVED FIXED	QA Contact:
Severity:	enhancement
Priority:	P5	CC:	janb, jesse.mcconnell, jetty-inbox
Version:	7.4.4
Target Milestone:	7.5.x
Hardware:	PC
OS:	Windows 7
Whiteboard:

Description Gili Mising name

2011-07-26 15:53:23 EDT

Build Identifier: 

Following up on http://dev.eclipse.org/mhonarc/lists/jetty-dev/msg00040.html and http://stackoverflow.com/questions/5170332/how-to-enable-java-assertions-in-jetty-maven-plugin we need a way to run jetty:run in a separate JVM and pass it a separate set of JVM options than Maven itself.

Reproducible: Always

Comment 1 Gili Mising name

2011-07-26 15:55:21 EDT

I am running version 6.1.26 but I believe this affects the 7.x plugin as well.

Comment 2 Gili Mising name

2011-07-26 16:22:26 EDT

I just tried version 7.4.4.v20110707. There doesn't seem to be any obvious way to pass JVM options to jetty:run so I believe the RFE applies to this version.

Comment 3 Jesse McConnell

2011-09-20 13:31:05 EDT

Dropping priority on this, its a nice idea and if someone would like to contribute a patch for this we can certainly take a look

Comment 4 Jan Bartel

2011-09-23 00:47:40 EDT

Gili,

See also codehaus jetty issues:
http://jira.codehaus.org/browse/JETTY-991

Comment 5 Jan Bartel

2011-09-28 01:57:39 EDT

Fixed for 7.5.2.

Use new <configuration> element <jvmArgs> with the mvn jetty:run-forked goal eg:


<jvmArgs>-verbose -Xprof -Dfoo=bar</jvmArgs>