You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Wim Deblauwe <wi...@gmail.com> on 2005/09/20 14:39:57 UTC
Re: [m1.1b1] log4j error
Is this solved in Maven 1.1 beta 2? Also what is the JIRA issue related to
this problem?
2005/8/25, Arnaud HERITIER <ah...@gmail.com>:
>
> you can safely ignore them
> we'll try to remove them as soon as possible.
> an issue is open in velocity
>
> Arnaud
>
> On 8/25/05, Wim Deblauwe <wi...@gmail.com> wrote:
> >
> > And is there a fix for it or can I safely ignore those errors?
> >
> > 2005/8/25, Arnaud HERITIER <ah...@gmail.com>:
> > >
> > > This is a problem between velocity 1.4 and log4J.
> > >
> > > Arnaud
> > >
> > > On 8/25/05, Wim Deblauwe <wi...@gmail.com> wrote:
> > > >
> > > > Hi,
> > > >
> > > > I get the following error in my build since I upgraded to Maven
> > 1.1beta1
> > > .
> > > > Any idea what might be the problem?
> > > >
> > > > log4j:ERROR Attempted to append to closed appender named [null].
> > > >
> > > >
> > > > I get that same line many, many times but the build seems to
> continue
> > > > fine.
> > > >
> > > > regards,
> > > >
> > > > Wim
> > > >
> > > >
> > >
> > >
> >
> >
>
>
Re: [m1.1b1] log4j error
Posted by Lukas Theussl <lt...@apache.org>.
The core doesn't use velocity, so you might just have to build the
plugins that depend on velocity [1] from sources. Actually, AFAICT, only
artifact, multiproject and xdoc use the velocity:merge tag. Just replace
the velocity dependency by a current snapshot (don't know if there's one
published, possibly have to build that from sources as well, and put it
in your local repo). You might have to do the same with
commons-jelly-tags-velocity. Run 'maven plugin:install' and you're set.
No guarantee, but let us know if it works! :)
-Lukas
[1]
http://maven.apache.org/maven-1.x/plugins/bundled/dependency-convergence-report.html#velocity-dvsl:velocity-dvsl
ysl2001 wrote:
> How can I patch my current m1.1b1 release with the patch. Can you provide
> some info. I am willing to
> give it a try as our production CC log file is really big and we can reduce
> the size by much as 80% if
> we can get rid of the
>
> log4j:ERROR Attempted to append to closed appender named [null]
>
> messages. Thanx.
> --
> View this message in context: http://www.nabble.com/-m1.1b1-log4j-error-t252755.html#a3891732
> Sent from the Maven - Users forum at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [m1.1b1] log4j error
Posted by ysl2001 <yo...@gmail.com>.
How can I patch my current m1.1b1 release with the patch. Can you provide
some info. I am willing to
give it a try as our production CC log file is really big and we can reduce
the size by much as 80% if
we can get rid of the
log4j:ERROR Attempted to append to closed appender named [null]
messages. Thanx.
--
View this message in context: http://www.nabble.com/-m1.1b1-log4j-error-t252755.html#a3891732
Sent from the Maven - Users forum at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [m1.1b1] log4j error
Posted by Lukas Theussl <lt...@apache.org>.
It's been tracked down to a memory leak in velocity [1] which is fixed
in the current development version, but as long as velocity-1.5 is not
released, the problem will persist in m1.1. It basically happens
whenever the velocity:merge tag is called more than once within one
jelly session, like in the xdoc:generate-from-pom goal.
-Lukas
[1] http://issues.apache.org/jira/browse/VELOCITY-193
ysl2001 wrote:
> Is this issue resolved? I searched thru jira, and other mailing list.
> Please let us know. Thanx
> --
> View this message in context: http://www.nabble.com/-m1.1b1-log4j-error-t252755.html#a3889224
> Sent from the Maven - Users forum at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [m1.1b1] log4j error
Posted by ysl2001 <yo...@gmail.com>.
Is this issue resolved? I searched thru jira, and other mailing list.
Please let us know. Thanx
--
View this message in context: http://www.nabble.com/-m1.1b1-log4j-error-t252755.html#a3889224
Sent from the Maven - Users forum at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [m1.1b1] log4j error
Posted by Arnaud HERITIER <ah...@gmail.com>.
Not it's not yet resolved :-(
I'll take a look at it.
I'm not sure that an issue was opened.
Arnaud
On 9/20/05, Wim Deblauwe <wi...@gmail.com> wrote:
>
> Is this solved in Maven 1.1 beta 2? Also what is the JIRA issue related to
> this problem?
>
> 2005/8/25, Arnaud HERITIER <ah...@gmail.com>:
> >
> > you can safely ignore them
> > we'll try to remove them as soon as possible.
> > an issue is open in velocity
> >
> > Arnaud
> >
> > On 8/25/05, Wim Deblauwe <wi...@gmail.com> wrote:
> > >
> > > And is there a fix for it or can I safely ignore those errors?
> > >
> > > 2005/8/25, Arnaud HERITIER <ah...@gmail.com>:
> > > >
> > > > This is a problem between velocity 1.4 and log4J.
> > > >
> > > > Arnaud
> > > >
> > > > On 8/25/05, Wim Deblauwe <wi...@gmail.com> wrote:
> > > > >
> > > > > Hi,
> > > > >
> > > > > I get the following error in my build since I upgraded to Maven
> > > 1.1beta1
> > > > .
> > > > > Any idea what might be the problem?
> > > > >
> > > > > log4j:ERROR Attempted to append to closed appender named [null].
> > > > >
> > > > >
> > > > > I get that same line many, many times but the build seems to
> > continue
> > > > > fine.
> > > > >
> > > > > regards,
> > > > >
> > > > > Wim
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>