[SUREFIRE-784] Surefire plugin cannot be debugged remotely by eclipse

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.10
• Fix Version/s: 2.11
• Component/s: process forking
• Environment: Eclipse indigo 20110916-0149; jdk1.6.0_27; Apache Maven 3.0.3 r1075438
• Assignee: Kristian Rosenvold
• Reporter: joseph vychtrle
• Created: 05/Nov/11 18:44
• Updated: 01/Sep/17 12:05
• Resolved: 29/Nov/11 16:38

Description

I'm talking about debugging the plugin/mojo, not tests.

Running maven with

-Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=8000

allows eclipse debugger to connect to the process of all maven plugins I tried, except for surefire-plugin.
The breakpoint in AbstractSurefireMojo just isn't triggered.

I tried everything possible
-DforkMode=once
-DforkMode=never
mvnDebug
etc.

Any idea how to deal with this ?

I would need to add 200 jars on classpath to boot up Liferay portal :

<additionalClasspathElements>
	<additionalClasspathElement>
		/opt/liferay/portal/lib/development/*
	</additionalClasspathElement>
	<additionalClasspathElement>
		/opt/liferay/portal/lib/global/*
	</additionalClasspathElement>
	<additionalClasspathElement>
		/opt/liferay/portal/lib/portal/*
	</additionalClasspathElement>
</additionalClasspathElements>

but it doesn't work. Neither *.jar wildcard ... Although

/opt/liferay/portal/lib/portal/c3p0.jar

works.

It is hard to figure out what is going on without debugging it.

Issue Links

• is related to: SUREFIRE-801 Classloading compatibility break with forkMode=NEVER in 2.9 and 2.10