That got it. It was the "inside jetty" part of the log4j impl I
didn't realize. Very cool quickstart, Howard.
Bill H.
On 10/28/07, Howard Lewis Ship <[EMAIL PROTECTED]> wrote:
> It is necessary that you upgrade the copy of log4j inside Jetty to version
> 1.2.14. That adds the isTraceEnabled():
The other warnings about unexpected symbols are caused by Tapestry and the
Maven archetype both using ${...} syntax. Fortunately, the archetype code
leaves ${...} it doesn't recognize alone.
On 10/28/07, Bill Holloway <[EMAIL PROTECTED]> wrote:
>
> There are some warnings thrown at the end of the
It is necessary that you upgrade the copy of log4j inside Jetty to version
1.2.14. That adds the isTraceEnabled():boolean method that SL4J expects.
On 10/28/07, Bill Holloway <[EMAIL PROTECTED]> wrote:
>
> There are some warnings thrown at the end of the new maven create
> archetype run, given by
