|
From: Loren R. <lo...@gm...> - 2004-09-14 18:59:41
|
moving over another e-mail thread. --- Torsten Juergeleit <tor...@t-...> wrote: > From: tor...@t-... (Torsten > Juergeleit) > Subject: Re: problems with latest version of Spring > IDE code > Date: Mon, 13 Sep 2004 22:32:36 +0200 > To: Loren Rosen <lor...@ya...>, > David Watkins <dav...@fa...> > > Sorry guys, I fixed the problem in BeanModel's > internal resource change > event handler (did wrong check for > 'isSpringProject()' event :-( ). > Changes are commited to CVS head. > > BTW, I created a mailing list for Spring IDE: > > https://lists.sourceforge.net/lists/subscribe/springide-eclip-developer > > Cheers, > Torsten > > > On 13.09.2004, at 18:45, Watkins, David wrote: > > > Hi Loren, > > I've been getting this with on my own (manual) > tests. Killing the > > runtime workspace and restarting it causes the > updated project to be > > seen and everything works. I think your diagnosis > is correct - it > > seems > > as if the 'add nature' action isn't updating the > BeansModel with the > > new > > project. I'd be very keen on getting the tests > checked in asap - are > > they in a separate plugin or within the existing > plugin modules? Once > > I've got the tests I'll see if I can add a fix as > it's beginning to bug > > me too! > > > > Cheers, > > dw > > > >> -----Original Message----- > >> From: Loren Rosen [mailto:lor...@ya...] > >> Sent: 13 September 2004 17:37 > >> To: Torsten Juergeleit > >> Cc: Watkins, David > >> Subject: problems with latest version of Spring > IDE code > >> > >> I've got my tests to compile and run the > springide-eclipse > >> code checked out from sourceforge. > >> This took some work to get the eclipse projects > configured, > >> but that's another story. The more immediate > problem is that > >> my tests fail. This is a regression from the > 1.0.3 release. > >> > >> The first test run is one that simply sets the > Bean project > >> nature, then unsets it. Before, after and > in-between it > >> checks that various eclipse attributes are as > they should be. > >> This test fails in the middle. > >> > >> Concretely, the test calls > >> BeansCoreUtils.addProjectNature() to add the bean > project > >> nature. Then it calls model.hasProject to check > that the > >> beans model knows about the project just added. > This check fails. > >> > >> If these test assertions are commented out, the > code then > >> calls BeansCoreUtils.removeProjectNature(), and > this gets a > >> NullPointerException, essentially for the same > reason that > >> hasProject() returns false. > >> > >> The other test failures come down to the same > cause. > >> > >> It looks as if the beans model in the newer code > is not > >> keeping things consistent with eclipse's own idea > of what > >> projects have what natures. It may be that this > code isn't > >> expected to be stable yet, but I thought you'd > want to know. > >> > >> I can check in my code now, but of course you'll > have to be > >> aware that the tests will fail. > >> > >> > >> > >> _______________________________ > >> Do you Yahoo!? > >> Shop for Back-to-School deals on Yahoo! Shopping. > >> http://shopping.yahoo.com/backtoschool > >> > > > > |