[
https://jira.codehaus.org/browse/SUREFIRE-784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=283239#comment-283239
]
Kristian Rosenvold commented on SUREFIRE-784:
---------------------------------------------
Exactly /why/ does the extract from ForkConfiguration explain anything ?
I have tried to reproduce /any/ of the symptoms/problems you describe here, and
try as I may I can't reproduce any of the problems you have. All is not lost,
though:
Make the necessary changes to demonstrate failure in an isolated example and
then upload the diff as a patch.
I somehow sense that your main problem is escape from the confines of the
isolated classloader, which is covered in the documentation
https://svn.apache.org/repos/asf/maven/surefire/trunk/surefire-integration-tests/src/test/resources/additional-classpath/
Unless you can produce a working isolated failing example, this issue will be
closed as cannot reproduce. If the problem would have been solved by improving
the documentation, do let us know what you think should be added.
> Surefire plugin cannot be debugged remotely by eclipse
> ------------------------------------------------------
>
> Key: SUREFIRE-784
> URL: https://jira.codehaus.org/browse/SUREFIRE-784
> Project: Maven Surefire
> Issue Type: Story
> Components: process forking
> Affects Versions: 2.10
> Environment: Eclipse indigo 20110916-0149
> jdk1.6.0_27
> Apache Maven 3.0.3 r1075438
> Reporter: lisak
>
> I'm talking about debugging the plugin/mojo, not tests.
> Running maven with
> {noformat}-Xdebug -Xnoagent
> -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=8000{noformat}
> 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 :
> {noformat}
> <additionalClasspathElements>
> <additionalClasspathElement>
> /opt/liferay/portal/lib/development/*
> </additionalClasspathElement>
> <additionalClasspathElement>
> /opt/liferay/portal/lib/global/*
> </additionalClasspathElement>
> <additionalClasspathElement>
> /opt/liferay/portal/lib/portal/*
> </additionalClasspathElement>
> </additionalClasspathElements>
> {noformat}
> but it doesn't work. Neither *.jar wildcard ... Although
> {noformat}/opt/liferay/portal/lib/portal/c3p0.jar{noformat}
> works.
> It is hard to figure out what is going on without debugging it.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
