Binary dependencies

[Peter Mateja]

Just curious why some of the binary dependencies (Moq, StructureMap,
etc) aren't checked into a location in the trunk. I see that Troy
specifically pulled Moq.dll from the tree. Ideally, we'd have these
living off the resource directory. It's kind of a pain to resolve
these, and at least in the test project that I pulled down, the Moq
dependency location is wrong (it's pointing to ..\..\..\..\lib\Moq
\Moq.dll in the test .csproj, but compilation-notes.txt directs us to
unzip into ..\..\..\..\lib\Moq.4.0.10827\NET35\Moq.dll.)

I think this'd be good for several reasons:
1) More consistent compilation environment for developers / builders
(repeatable, standard builds)
2) Explicit inclusion of the version of dependencies on which the
trunk / branches rely.

I'd think that the only thing standing in the way might be specific
licensing issues.

[Troy Howard]

There's a discussion on this topic right now in the lucere-dev mailing
list. Feel free to take part in it. We're in the middle of deciding
what to do about that.

Thanks,
Troy

> --
> You received this message because you are subscribed to the Google Groups "Lucere" group.
> To post to this group, send email to luc...@googlegroups.com.
> To unsubscribe from this group, send email to lucere+un...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/lucere?hl=en.
>