Your best bet is to write an issue here: http://jira.codehaus.org/browse/MSUREFIRE and attach your patch. This way it won't get lost.
-----Original Message----- From: Raif S. Naffah [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 15, 2006 4:59 PM To: dev@maven.apache.org Subject: patch for surefire plugin to make it more Eclipse-friendly hello there, the attached patch checks first if the 'test' env-var value ends with ".java" or not before constructing the reg-exp for single/specific tests. with this patch, Eclipse users can select a test and run one external tool similar to the following: <?xml version="1.0" encoding="UTF-8"?> <launchConfiguration type="org.maven.ide.eclipse.Maven2LaunchConfigurationType"> <listAttribute key="M2_PROPERTIES"> <listEntry value="test=${resource_name}"/> </listAttribute> <stringAttribute key="M2_GOALS" value="test"/> <stringAttribute key="org.eclipse.debug.core.ATTR_REFRESH_SCOPE" value="${project}"/> <listAttribute key="org.eclipse.debug.ui.favoriteGroups"> <listEntry value="org.eclipse.ui.externaltools.launchGroup"/> </listAttribute> <stringAttribute key="org.eclipse.jdt.launching.WORKING_DIRECTORY" value="${workspace_loc:/xxx"/> </launchConfiguration> cheers; rsn --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
