Looks like I'm back up and running! On Tue, Mar 2, 2010 at 11:52 AM, Sebastian Hennebrueder <[email protected]> wrote: > I'll stay with my non Eclipse IDEs. Just can't live with broken workspaces > and plugin nightmares. ;-) > > > Ulrich Stärk schrieb: >> >> Ahh yes... the good Eclipse update mechanism... I remember having trouble >> updating the exact same plugin some days ago. Unchecking the "Contact all >> available update sites" checkbox did the trick for me. Oh. and don't use the >> "check for updates" feature. Just try to install the plugin in the newer >> version, Eclipse will do an update if there is a newer version. >> >> Uli >> >> Howard Lewis Ship schrieb: >>> >>> Looks like there is an update, but Eclipse is being terrible about >>> getting it ... keeps hanging. Hey folks! I'm off Twitter, so I'm >>> venting here now! >>> >>> >>> On Tue, Mar 2, 2010 at 11:23 AM, Howard Lewis Ship <[email protected]> >>> wrote: >>>> >>>> Very wierd stuff ... the tests no longer run for me in Eclipse! There >>>> seems to be a classpath problem with TestNG. I tried upgrading to >>>> 5.11 with no luck. It all works fine from the command line. >>>> >>>> Full refresh, full clean all, .classpath files up-to date and I get >>>> wierd errors: >>>> >>>> org.testng.TestNGException: >>>> Method startup requires 6 parameters but 4 were supplied in the >>>> @Configuration annotation. >>>> at >>>> org.testng.internal.Parameters.checkParameterTypes(Parameters.java:152) >>>> at >>>> org.testng.internal.Parameters.createParameters(Parameters.java:97) >>>> at >>>> org.testng.internal.Parameters.createParameters(Parameters.java:280) >>>> at >>>> org.testng.internal.Parameters.createConfigurationParameters(Parameters.java:71) >>>> at >>>> org.testng.internal.Invoker.invokeConfigurations(Invoker.java:143) >>>> at >>>> org.testng.internal.Invoker.invokeConfigurations(Invoker.java:88) >>>> at org.testng.TestRunner.beforeRun(TestRunner.java:510) >>>> at org.testng.TestRunner.run(TestRunner.java:478) >>>> at org.testng.SuiteRunner.runTest(SuiteRunner.java:332) >>>> at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:327) >>>> at org.testng.SuiteRunner.privateRun(SuiteRunner.java:299) >>>> at org.testng.SuiteRunner.run(SuiteRunner.java:204) >>>> at org.testng.TestNG.createAndRunSuiteRunners(TestNG.java:877) >>>> at org.testng.TestNG.runSuitesLocally(TestNG.java:842) >>>> at org.testng.TestNG.run(TestNG.java:751) >>>> at org.testng.remote.RemoteTestNG.run(RemoteTestNG.java:73) >>>> at org.testng.remote.RemoteTestNG.main(RemoteTestNG.java:124) >>>> >>>> >>>> Looking into it more ... I think that the TestNG plugin is overriding >>>> the version of TestNG used when running the tests. Ouch! I'm >>>> checking for an updated TestNG plugin; has anyone else encountered and >>>> overcome this issue? >>>> >>>> >>>> -- >>>> Howard M. Lewis Ship >>>> >>>> Creator of Apache Tapestry >>>> >>>> The source for Tapestry training, mentoring and support. Contact me to >>>> learn how I can get you up and productive in Tapestry fast! >>>> >>>> (971) 678-5210 >>>> http://howardlewisship.com >>>> >>> >>> >>> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > > > -- > Best Regards / Viele Grüße > > Sebastian Hennebrueder > ----- > Software Developer and Trainer for Hibernate / Java Persistence > http://www.laliluna.de > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
-- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
