Re: [MO-java-dev] Why is it so complicated???

[Nat P. <nat...@b1...>]

> Its certainly not easy to just pull this down in eclipse and use it...
there
> are jdk versions to worry about (yes I know this is an issue but only for
> very advanced stuff - surely?), and the directory structures don't easily
> map into the eclipse view of the world (I guess you guys all use some
> complicated scheme in intellij? But why not use eclipse as the lowest
common
> denominator?

I'm using Eclipse and have had no problem bringing the MO CVS repository
into Eclipse.  Yes, it's a bit more involved than the projects that are
created by Eclipse's wizards, but then it has to deal with more complicated
issues such as supporting multiple versions of the JDK in one project.  Can
you describe the problems you've had with Eclipse in more detail?

> Having played with the dynamic mock stuff I am suprised that all the
people
> that I've seen post messages about using it - haven't complained about the
> horrible error messages (the original non dynamic version went to great
> pains to provide useful error messages that would help you quickly locate
an
> error and fix it - see my paper A Plea for Assert Equals). I'm also
suprised
> no-one has needed an UnorderedExpectationList... I think this is really an
> indication that people just haven't used this stuff in anger, or seen how
it
> works at connextra to know that there is much better.

The dynamic mocks can be improved in many ways.  Unfortunately I've been
offline for a couple of months while working in Africa and have not had a
chance to put as much effort into the project as I'd have liked.  Now that
I'm back I will be conferring with Joe, Steve F and other mockistas to make
sure that the dynamic package evolves in a good direction.  Help is always
appreciated.  Could you describe how you think error messages can be
improved?

Cheers,
            Nat.