Hi Gurkan! > I think its source code always stay in its own module, so it > is not necessary to move its source code into the webbeans-impl > module.
I was thinking about having the TCK tests in webbeans-impl also because of the release process. One should imho never be able to deploy webbeans-impl _without_ running the TCK tests. That's the reason why those tests are usually maintained as integral part of the main project. But let's simply count the pros and cons. But for now we have to create a separate module anyway, and a SVN move will be no problem later if needed. LieGrue, strub --- Gurkan Erdogdu <[email protected]> schrieb am Fr, 16.1.2009: > Von: Gurkan Erdogdu <[email protected]> > Betreff: Re: tck integration > An: [email protected] > Datum: Freitag, 16. Januar 2009, 20:15 > Its great Mark. I prefer to create another module for > integrating the TCK (+1). > > The other module's folder names are started with > webbeans, so this module name can be webbeans-tck. I think > its source code always stay in its own module, so it is not > necessary to move its source code into the webbeans-impl > module. > > Thanks; > > /Gurkan > > > > > ________________________________ > From: Mark Struberg <[email protected]> > To: [email protected] > Sent: Friday, January 16, 2009 9:06:13 PM > Subject: tck integration > > Hi! > > FYI: yesterday night, I started integrating the TCK from > the webbeans RI into openwebeans-impl. > > I'm currently using the 1.0.0-SNAPSHOT and will _not_ > checkin the changes into the mainline until there is an > official TCK released. > > The problem is that even if I omit the execution of the TCK > via a profile, I still need at least the > org.jboss.webbeans.tck:webbeans-tck-api otherwise the tests > will not compile. So everyone who likes to build the TCK for > openwebbeans has to build the jboss TCK modules first in his > local environment - which is not acceptable to be checked > in. > > I maybe could do the TCK integration in a separate module > openwebbeans-tck in the meantime, and if it finally works, > we could move all the code and configuration over to > openwebbeans-impl. > > Another way would be to develop this solely in git until we > reached this point and move it over to SVN later. > > LieGrue, > strub
