[Lumberjack-devel] Re: Clarification (was pl. help)

[Chandrasekhar B. <ba...@te...>]

Matt,

Now I know the source of all confusion.  Its me, but not my programming!
Looks like there is another Lumberjack, the logging API implementation on
sourceforge.net.  The first time I downloaded the stuff, I forgot to bookmark
and the next time I searched for it for mailing my problem, I found the other
one.  I found a different name under developer and was surprised, but thought
it was a change.  Now I searched Sourceforge again and found the other
Lumberjack too.

Sorry for the confusion,
Balla


Matt Luker wrote:

> ko...@re... wrote:
> > I'm going to go out on a limb here, but if you put your test class in
> > the package java.util.logging it will send that request to the
> > bootloader--which is native.  It would be my guess that the exception
> > you are encountering is the bootloader becoming very confused or dying
> > because it thinks it has a critical error or security breach.
> >
> > Using the lumberjack-0.8.1 package and JDK 1.2.2, I was able to get it
> > running and working using the instructions in the READMEs.
> >
> > The classes are under com.redstarhackers.lumberjack.*.
>
> I stated what I think the problem is, but not the solution ... oops!
>
> I would move your class from java.util.logging to balla or some default
> package.  The java.* packages are reserved and I would be unsure how
> putting a class in that tree would behave on all platforms.
>
> Instead of java.util.logging, call it balla.logging or com.techone.logging.
>
> Let me know if that helps.
>
> Matt