sorry that I haven't followed this thread close enough. . .could
someone recap on why we want to make log4j the implementation we
choose? what's wrong with just using SimpleLog - since eveything else
we're gearing towards is simple/lightweight?

David

On 2/9/06, Zhong ZHENG <[EMAIL PROTECTED]> wrote:
> pom updated to include log4j.
>  Thanks Patrick!
>
>
> On 2/8/06, Patrick Huber <[EMAIL PROTECTED]> wrote:
> > Hi
> >
> > I'm still having the same problem. The log4j.jar is not included in
> > pluto-portal.war per default - the pom doesn't reference log4j as
> > dependency. The entry I added looks like this (copied from the
> > testsuite):
> >     <dependency>
> >       <groupId>log4j</groupId>
> >       <artifactId>log4j</artifactId>
> >       <version>1.2.9</version>
> >       <scope>runtime</scope>
> >     </dependency>
> >
> > After a mvn clean install; mvn pluto:install
> > -DinstallDir=$CATALINA_HOME, log4j.jar is included in the war file.
> >
> > Would you mind doing a fresh svn co to check if you get this same
> > error or not? So we'd know for sure if this is a local problem on my
> > end or not.
> >
> > --
> >
> > Update: I just tried another thing: delete pluto and testsuite from
> > the webapp directory and that seemed to do the trick. Even though the
> > tomcat install was fresh too, there must have been some leftovers from
> > a previous attempt...
> >
> > Sorry for bothering you
> > Patrick
> >
> >
> > --
> > "I love deadlines. I like the whooshing sound they make as they fly
> > by." -- Douglas Adams
> >
>
>
> --
>
> ZHENG Zhong
>  - http://heavyz.blogspot.com/
>  - http://people.apache.org/~zheng/
>

Reply via email to