Subject: -- misplaced calls to setJarByClass

I want to point out that option (2) is thinkable for 0.5, since it
does not require adding/changing the API of every single driver we
have (just the implementation), and is compatible. It also does not
preclude the others.

If no one writes anything to discourage me, I'm prone to do it. The
only problem I see is that of people trying to submit the example jar
while specifying a class name that is in the core jar. Option 2 does
not cure the need to unpack the core jar in the example jar. I guess
for 0.5 we could leave the example jar working this way, and pat
ourselves on the back for sparing users the need to unpack

On Fri, Apr 8, 2011 at 3:17 PM, Ted Dunning <[EMAIL PROTECTED]> wrote: