Upon further inspection though, it looks like while the build finished, it was reporting zero coverage, even the tests were not all run.
You can see the most current version of my pom here: http://gist.github.com/40019 Is there anything weird going on here? - Kevin On Dec 26, 12:32 am, Kevin Fitzpatrick <[email protected]> wrote: > Cool. That seemed to do the trick :) > > So if I understand this correctly, by scoping the testing-support bit > to just the test phase, we prevented the unused references from being > compiled outside of the testing phase, thus preventing the errors. > > Awesome. > > Thanks, > Kevin > > On Dec 25, 6:02 pm, "RedBugz Software" <[email protected]> wrote: > > > On Thu, Dec 25, 2008 at 1:53 PM, Kevin Fitzpatrick > > > <[email protected]> wrote: > > > Do I need to include dependency nodes for each of the unit test > > > frameworks? (i.e. ASUnit, Fluit & FlexUnit) > > > I don't think so. The testing-support pom has all of those listed as > > their > > dependencies:http://svn.sonatype.org/flexmojos/repository/info/flex-mojos/testing-... > > > > When I include the testing-support dependency using > > > > <dependency> > > > <groupId>info.flex-mojos</groupId> > > > <artifactId>testing-support</artifactId> > > > <version>2.0M10</version> > > > <type>swc</type> > > > </dependency> > > > > I end up with these compiler errors: > > > <snip>...... > > > Try adding <scope>test</scope> to the above dependency. That might > > solve the problems. > > > Logan --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Flex Mojos" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/flex-mojos?hl=en?hl=en http://blog.flex-mojos.info/ -~----------~----~----~----~------~----~------~--~---
