Thanks to Stefan for clarification.
As a workaround I use System.getProperty("XmlLogger.level") instead of
event.getProject().getUserProperty("XmlLogger.level") to get the desired
logging level.
The only problem with this approach is that I have to call Ant via java call
like this:
"%JAVA_HOME%\
On Thu, 10 Jul 2008, <[EMAIL PROTECTED]> wrote:
> Thanks to Stefan for clarification. As a workaround I use
> System.getProperty("XmlLogger.level") instead of
> event.getProject().getUserProperty("XmlLogger.level") to get the
> desired logging level. The only problem with this approach is that
>
Hello everyone.
I've created my own listener CustomXmlLogger that is a child of XmlLogger
and packed it in VCS.jar. I don't want to copy it to ANT_HOME/lib so I tried
to include a reference to the archive in my Ant call.
But I've got a problem. When I launch a build Ant indicates on LinkageError:
Thank you to the Ant team for rolling out Ant 1.7.1
I have started the ball rolling to have Eclipse 3.5 incorporate Ant 1.7.1.
Follow bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=209504 to watch
the action.
Thanks again
Darins
http://runnerwhocodes.blogspot.com/
Stefan Bodewig <[EMAIL P
On Thu, 10 Jul 2008, <[EMAIL PROTECTED]> wrote:
> Hello everyone. I've created my own listener CustomXmlLogger that
> is a child of XmlLogger and packed it in VCS.jar. I don't want to
> copy it to ANT_HOME/lib so I tried to include a reference to the
> archive in my Ant call. But I've got a prob
