Re: Weird classpath issue using DefaultConfiguration during unit testing

From: Cris Daniluk (cris.danilu..mail.com)
Date: Fri Jun 24 2005 - 11:44:19 EDT

  • Next message: Mike Kienenberger: "Re: Weird classpath issue using DefaultConfiguration during unit testing"

    The classpath notation specified in getResource actually specifies
    that the / should not be used, so I think you could strip it without a
    problem.

    In fact, that's probably what Jetty did for you...

    On 6/22/05, Andrus Adamchik <andru..bjectstyle.org> wrote:
    > I guess instead of saying "don't put a forward slash in the path", in the
    > future we may change the code to quietly strip it to make the whole thing
    > more robust. I can't think of any side effects...
    >
    > Andrus
    >
    >
    > > Andrus Adamchik <andru..bjectstyle.org> wrote:
    > >>
    > >> Haven't used this in a while, but is it possible that leading "/" causes
    > >> the problem? Per our own JavaDocs:
    > >>
    > >> .. Format should be "my/package/name" without leading "/"...
    > >
    > > Yeah, that was the problem! Thanks.
    > >
    > > The leading "/" must not have been an issue in the Jetty classloader since
    > > I
    > > had no problems with it there.
    > >
    >
    >



    This archive was generated by hypermail 2.0.0 : Fri Jun 24 2005 - 11:44:21 EDT