Its fixed now. I'm not sure what the cause was but it seamed like my changes to the tckbase weren't being applied when building the core.
On May 18, 2013 11:02 AM, "Kurt T Stam" <[email protected]> wrote: > > > > > On 5/17/13 7:40 AM, Alex O'Ree wrote: >> >> I'm running into an issue with a failing unit test when building the >> juddi-core module >> >> org.apache.juddi.subscription.SubscriptionNotifierTest >> in the path >> juddi-core\src\test\java\org\apache\juddi\subscription >> >> I'm getting two failures. One is the test case itself, the other is >> thrown during the cleanup operating. From what I can tell, the >> subscription service that's created during "setup" phase doesn't >> appear to be executing. > > Weird. maybe you have a compile issue that prevents it from executing. Also eclipse > keeps its classes elsewhere, so be aware that you may have to 'clean' your project > in eclipse to get it to build again. This is an eclipse quirk though. Nothing much > our build can do about that. > >> >> This particular function is in the tck-base TckBusinessService. I've >> been attempting to insert debugging statements into this file and my >> changes do not appear to be propagating. Is this a "maven/ant copy >> classes around" problem, or am I missing something? Changes to the >> SubscriptionNotifierTest are executing, but not stuff in >> TckBusinessService. > > We have 2 juddi-core modules, because the persistence binary code gets enhanced by the > JPA provider (for openjpa anyway), hibernate enhances at runtime, so it leave the binary > code alone. So if we want to run the unittests for both hibernate and openjpa, then we > need to compile twice. Hence the two modules. The core-openjpa version gets it's source > files form copying them from the core module, this so we don't have the code in two places. > We don't copy any other code around. > > The uddi-tck-base is a dependency on both juddi-core as well as uddi-tck. So the maven reactor > compiles uddi-tck-base first and then uses that in the uddi-tck and juddi-core. If you do not > run the maven build from the root, then it is up to you to recompile uddi-tck-base first. > > If you use m2eclipse, and you only have each module as a project, then it will create a project > level dependency and changes are automatically propagated. > > >> >> Any ideas? I've of course tried, mvn clean install and did a file >> search to see if there were any duplicate copies of the tck test >> somewhere > > No clue what's going on on your machine, sorry..
