On Fri, May 8, 2009 at 5:00 PM, ant elder <[email protected]> wrote: > On Fri, May 8, 2009 at 4:43 PM, Simon Laws <[email protected]> wrote: >> On Fri, May 8, 2009 at 4:39 PM, Simon Laws <[email protected]> wrote: >>> On Fri, May 8, 2009 at 4:33 PM, ant elder <[email protected]> wrote: >>>> On Fri, May 8, 2009 at 4:16 PM, Simon Laws <[email protected]> >>>> wrote: >>>>>> >>>>>> Yes its the first of those. The sample/helloworld-bpel will show the >>>>>> problem, if running in eclipse you need to build with mvn first so >>>>>> that the Ode database gets unzipped into target\test-classes folder >>>>>> and added to the classpath. >>>>>> >>>>>> ...ant >>>>>> >>>>> >>>>> K, I don't even get that far. I get a NPE on the reference side >>>>> running helloworl-bpel. Just updating again to make sure I've not >>>>> missed anything. >>>>> >>>>> Simon >>>>> >>>> >>>> Everything i have is checked in now so it should be working, what is >>>> the NPE you get? >>>> >>>> ...ant >>>> >>> It did pick up a few things in the update so let me recompile and see >>> if it goes away (fingers crossed). >>> >>> Simon >>> >> Right, got past one problem with an unneeded import but now have >> problems with binding-rmi-runtime and node-laucher-equinox. Are you >> getting a clean build? >> >> Simon >> > > I've not done a full build since earlier, will do one now... > > ...ant > Right, I'm getting a bit further. After much messing about with Eclipse I'm getting past the node-laucher-equinox problem at least. Waiting for the rest of the build to complete. I seem to have all kinds of problems when modules are moved around and I then try and to so a maven build with Eclipse open. It's difficult to put my finger on it but sorting the Eclipse build out means that mvn works properly?
Simon
