Re: Debugging Plugin

Thanks for posting that, Benjamin. I've filed SUREFIRE-436 that we should update the site documentation to include a more explicit debugging tutorial (at least for debugging forked tests). You both may note that I've posted a long rant about the bug Andreas is interested in (SUREFIRE-433) o

[jira] Subscription: Design & Best Practices

Issue Subscription Filter: Design & Best Practices (29 issues) Subscriber: mavendevlist Key Summary MNG-2184Possible problem with @aggregator and forked lifecycles http://jira.codehaus.org/browse/MNG-2184 MNG-612 implement conflict resolution techniques htt

Re: Debugging Plugin

Why? I want fix some testng-bugs ;) :-) Pleas can anyone tell me : how can i debug a running surefire-plugin (e.g. in Eclipse) You can setup a "Remote Java Application" launch configuration via the menu command "Run" > "Open Debug Dialog...". The "Project" could be one of the Surefire module

Debugging Plugin

Hello folks, i try to understand the internals of the surfire-plugins (api, report, testng-provider). Why? I want fix some testng-bugs ;) First i try to fix the bug "ignoring the defined testng-suite-name and use allways 'TestSuite'" ... i don't undertstand where the suitefiles parsed (i guess an

[MNG-3140] how to get the ${basedir} value from a Plexus component ?

Hello, I'd like to fix MNG-3140 (add support for ${basedir} property in profile activation). MNG-2363 and MNG-3017 seems to also relie on File path beeing relative to working directory. I'd like to use the PathT

Re: http://jira.codehaus.org/browse/MCHANGES-78

Hi, Really nice ! Hope that it will be integrated in the maven-changes-plugin and released soon. Rémy

http://jira.codehaus.org/browse/MCHANGES-78

Hi, I have updated the code for this enhancement. It parses svn messages to produce the changelog in the site. This way you don't have to maintain a changes.xml file. Now it uses Maven-SCM API and it is Java 1.4 compliant. regards, Emmanuel