Chad-- Hey -- I deleted my controls/ sub-directory, refreshed it from SVN, rebuilt all of trunk/, ran the tests, and they passed. Seems like there's something stale that's causing this problem.
Perhaps that's the problem with the CC machine? Eddie On 7/7/06, Chad Schoettger <[EMAIL PROTECTED]> wrote:
Thanks Eddie, I'll take another look at the test failure and try to get it resolved today. - Chad On 7/7/06, Eddie O'Neil <[EMAIL PROTECTED]> wrote: > Chad-- > > I've seen a couple of problems here. The first is that the > .beaninfo files that are committed to the src/... tree are out of date > with the new package names and need to be re-generated. The Ant that > updates them should be updated as well to reflect new classpath / > package names (this target is in controls/test/build.xml). > > The other problem is likely caused by having moved a ControlBean > from the TCH tests to the JUnit tests. The TCH control beans were > used by both the standalone TCH tests and the webapp TCH tests -- the > classes in o/a/b/c/t/c/generic don't seem to be in the > controlstestbeans.jar file that is copied into the webapp. That > causes the compile error in the CC logs and that I see locally. > > Personally, I don' t really have an opinion about having Page Flow > specific tests in the Controls package. It makes it harder for > Controls committers to test Page Flow if they're moved to the NetUI > tree, but it also loosely couples the modules. If the Controls tests > do move to the NetUI tree, you can take advantage of the existing > infrastructure for the test recorder and avoid building new webapp > test infrastructure for Controls. > > Hope that helps... > > Eddie > > > On 7/6/06, Chad Schoettger <[EMAIL PROTECTED]> wrote: > > I'm looking into this failure, right now I am having a bit of trouble > > reproducing locally. > > > > - Chad > > > > On 7/6/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > View results here -> http://beehive01.bea.com/cruisecontrol/buildresults?log=log20060706121849 > > > > > >
