[Swift-devel] including non-standard providers in Swift builds

[Michael Wilde]

On 7/29/08 1:45 AM, Ben Clifford wrote:
> On Mon, 28 Jul 2008, Michael Wilde wrote:
> 
>> I ask this because the line I show above does not seem to consistently build
>> both providers. Yesterday I was getting deef but no coaster; today I'm getting
>> coaster but no deef. I havent tried enough experiments (or reading) to figure
>> this out yet.
> 
> How did you check whether it was building the providers or not? Watching 
> the build messages? Looking at the lib/ directory in the distribution for 
> the appropriate jars? Trying to run wift using those providers?

The latter. essentially find | egrep 'def|coaster' from the root of dist 
would show now jars of one or the other, and it would give a missing 
provider message at runtime.

I'll try the -v and look at the messages and report back.