Nice one. Adding an svn:ignore to a new project/module's target directory is about the first thing I do for a new artifact.
Brett On 3/16/10, Randall Fidler <[email protected]> wrote: > Finally! As suspected... it was some stupid trivial item. I'm posting this > just so the thread on the mail archive will be complete. > > Effectively what was causing the issue was some of surefire reports got > checked into the scm under the target directory > {project}/target/surefire-reports. This is what caused surefire via release > plugin to fail on the perform goal and not the prepare goal. Reason being > is that prepare runs a clean (and I usually run mvn clean release:prepare > anyhow) as it's first step. When the release goal was running, it would > check out the entire project again to {project}/target/checkout/ in which > those same surefire reports that were in the scm, would be placed into > {project}/target/checkout/target/surefire-reports. As a consequence, the > surefire plugin would bomb on perform and not prepare (because prepare > deleted them via it's own clean execution). Perform would does not run a > clean so when it checked out the entire project again, the reports were in > the target directory which throws surefire for a loop. > > I wish surefire would give you more information, such as it had a problem > with a report file already existing, that would have saved SO much time, oh > well. > > Lesson learned: Make sure you don't check anything into your projects target > directory on your SCM, IT'S NOT A GOOD IDEA! ;) > > > Regards, > > Randall > > -----Original Message----- > From: Randall Fidler [mailto:[email protected]] > Sent: Monday, March 15, 2010 1:32 PM > To: Maven Users List > Subject: RE: Test fail for release:perform only - no failure info > > Wayne, > > One issue... how do you get the "maven.surefire.debug" option to the > surefire plugin since it's running via the release plugin? For instance, if > I try to tell it just to skip tests, (i.e. -Dmaven.test.skip=true) it won't > because the release plugin has it's own surefire config (I'm guessing). So > even if I want to debug it using Eclipse to attach to the test jvm, I don't > see how can I get that parameter to the surefire instance that the release > plugin is firing up. I'll try anyhow, but think this will be a problem. > > Regards, > > Randall > > -----Original Message----- > From: Wayne Fay [mailto:[email protected]] > Sent: Monday, March 15, 2010 1:14 PM > To: Maven Users List > Subject: Re: Test fail for release:perform only - no failure info > >> I read somewhere that you can hook a debugger to the surefire plugin, >> is that what you're talking about? I believe that plugin has a parameter >> that tells it to wait until the "debugger" has connected and then it >> proceeds >> to run the tests. > > Googling "maven surefire debugger" brought the proper results to the > top... give it a try. ;-) > > Wayne > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Sent from my mobile device --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
