I think that we could add another profile for CDI TCK testing, and exclude the TestNG from the jsr299-tck-impl. Will try it today.
2010/9/5 Stephen Connolly <[email protected]> > I might have a look see... but > http://jira.codehaus.org/browse/SUREFIRE-141is probably more important > > On 3 September 2010 23:27, David Blevins <[email protected]> wrote: > > > > > On Sep 3, 2010, at 2:45 PM, Stephen Connolly wrote: > > > > > Perhaps the thing would be to split the CDI TCK into a separate module > > that > > > way it could be run using TestNG leaving the other tests as is on JUnit > > > > It's looking like that might be the only option. Very silly as it would > be > > nice to be able to write more TestNG stuff without having to completely > > ditch all JUnit support. > > > > I'm pretty surprised no one has just written a runner that can do both. > > Seems like that would be easy. > > > > > > -David > > > > > > > > > > On 3 September 2010 16:05, Jean-Louis MONTEIRO < > > > [email protected]> wrote: > > > > > >> > > >> Hi Stephen, > > >> > > >> Thanks. > > >> I now have all tests running again. > > >> > > >> The problem is that OpenEJB uses JUnit but CDI TCK (provided by JBoss) > > >> comes > > >> with TestNG. > > >> So, from my understanding we need to use JUnit for our tests and > TestNG > > for > > >> CDI TCK. > > >> > > >> I tried only using TestNG because it's actually able to run JUnit > tests > > but > > >> I get the infinite loop Jarek mentioned. > > >> > > >> After digging into Surefire JIRA, i found a small work around (See rev > > >> 992320) that seems to work for me. > > >> If someone else can give it a try, that'd be great! > > >> > > >> Jean-Louis > > >> -- > > >> View this message in context: > > >> > > > http://openejb.979440.n4.nabble.com/Re-svn-commit-r991445-in-openejb-trunk-openejb3-container-openejb-core-openejb-core-src-main-java-orp-tp2403609p2525814.html > > >> Sent from the OpenEJB Dev mailing list archive at Nabble.com. > > >> > > > > > -- Ivan
