Re: null system properties in buildStarted()

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 >

Re: null system properties in buildStarted()

ogger Because ant.bat doesn't set -D= arguments as system properties. -- View this message in context: http://www.nabble.com/null-system-properties-in-buildStarted%28%29-tp18294458p18377522.html Sent from the Ant - Dev

Re: null system properties in buildStarted()

On Sat, 5 Jul 2008, <[EMAIL PROTECTED]> wrote: > I'd like to know why properties are not defined in buildStarted(). The primary reason is that setting properties will create messageLogged events which means listeners would receive build e

null system properties in buildStarted()

} Output: D:\home\UMC\.garbage>ant -lib VCS.jar -listener com.kvazarmicro.umc.vcs.utils.Cu stomXmlLogger -DXmlLogger.file=build_test_log.xml -DXmlLogger.level=ERR Buildfile: build.xml fileStr = null levelStr = null test: tar1: [echo] Still alive tar2: [echo] Still alive BUILD SUCCESSFUL