I'm not a Maven expert, so please be very explanatory in your answers if possible. It looks like that only works because it turns off all the plugins in question.....I have now also tried m2e 1.0.0 via this update site and still get the same error. In the Maven world, there is a difference between the two - the former defines "if you happen to use this plugin, here's the configuration to use", whereas the latter states "use this plugin". Taking them out entirely would also work, but I'm assuming they're in there for a reason?Serenity tells you not only what tests have been executed, but more importantly, what requirements have been tested.Serenity BDD provides strong support for automated web tests using Selenium 2, though it also works very effectively for non-web tests such as tests that exercise web services or even call application code directly.We also encourage users to join our IRC channel (#jruby on Freenode) and mailing lists. JRuby 1.7.27 is our latest update release of JRuby 1.7.x.The primary goal of 1.7 point releases is to fill out any missing compatibility issues with Ruby 1.9.3.
Here is a snip from my for the plugin that is causing the issues...
The aim of Serenity is to make it easy to quickly write well-structured, maintainable automated acceptance criteria, using your favorite BDD or conventional testing library.
You can work with Behavior-Driven-Development tools like Cucumber or JBehave, or simply use JUnit.
Tycho supports the build process of Eclipse plug-ins, OSGi bundles, Eclipse features and update sites (based on p2) and products.
Combined with a continuous integration server, e.g., a Jenkins instance, Tycho allows a continuous integration build.
Serenity BDD is commonly used for both Automated Acceptance Tests and Regression Tests, and the principles discussed here apply, with minor variations, to both.