----- Original Message -----
Sent: Tuesday, October 21, 2003 11:37
AM
Subject: RE: [Nant-users] Logging
failures or successes
Hi Gert
Using record with level led to next Internal Error
I use next directive in nested build tasks. May be
action must be different ?
<record name="${root.dir}\Release.log" action="" autoflush="false"
verbose="true"/>
[license] Compiling license file c:\acrm\src\Core\Oblik.DMS\licenses.licx to
C:\DOCUME~1\amid.BKC\LOCALS~1\Temp\btk9v8jm\Oblik.DMS.dll.licenses using
target c:\acrm\Oblik.DMS.dll.
BUILD FAILED
INTERNAL ERROR
System.Runtime.Serialization.SerializationException: The type
NAnt.Contrib.Util.FileLogListener in Assembly NAnt.Contrib.Tasks,
Version=0.1.0.0, Culture=neutral, PublicKeyToken=null is not marked as
serializable.
Server stack trace:
at
System.Runtime.Serialization.FormatterServices.InternalGetSerializableMembers(RuntimeType
type, Boolean excludeNonSerializable)
Regards,
Dmitry Bezuglyy
[EMAIL PROTECTED]
> -----Original Message-----
>
From: Gert Driesen [mailto:[EMAIL PROTECTED]]
> Sent: Monday, October 20, 2003 9:43 PM
> To: Nicklas Norling; 'N. V.';
[EMAIL PROTECTED]
> Subject: Re:
[Nant-users] Logging failures or successes
>
> Are you closing (not just stopping) the
Release.log recorder
> in your "failure" target
?
>
> I attached an
example of a working build file.
>
> Note, when you close the Recorder in the failure target, the
> final build result will not yet have been written
to the log,
> so I don't think its useful for you
anyway. I don't think we
> can change this
behaviour as this would mean that the build
>
output that's generated in the failure target will not be
> available to other loggers that send out the results when the
> BuildFinished event is raised.
>
> Gert
>
> ----- Original Message -----
> From: "Nicklas Norling" <[EMAIL PROTECTED]>
> To: "'N. V.'" <[EMAIL PROTECTED]>;
> <[EMAIL PROTECTED]>
> Sent: Monday, October 20, 2003 9:28 AM
> Subject: RE: [Nant-users] Logging failures or successes
>
>
> > Sorry to say, this did not work either. The logfile is
> > still locked, even with autoflush turned on.
> >
> > C:\Harv> nant
release
> >
>
> <target name="release" depends="init">
> > <record name="Release.log"
action="" autoflush="true"/>
>
> <property name="debug"
value="false"/>
> >
<nant buildfile="${build.dir}\src\default.build"
> target="release"/>
>
> <nant
buildfile="${build.dir}\Documentation\demo.build"
>
> target="release"/>
>
> <record name="Release.log"
action=""/>
> >
</target>
> >
>
> ziplogs:
> >
>
> [zip] Zipping 2 files to
C:\Harv\BuildLogs.zip.
> >
C:\Harv\main.build(69,6):
> > Zip file
'C:\Harv\BuildLogs.zip' could not be created.
>
> The process cannot access the file "C:\Harv\Release.log"
> because it is
> >
being used by another proces
> >
> > The ziplogs target is called on
> > <property name="nant.onfailure"
value="failure" />
> >
> > Maybe I should report this as a bug on either NAnt or
NAntContrib?
> > Shurely this ought to work for
effective logging?
> >
> > /Nicke
> >
> > -----Original Message-----
> >
From: Nicklas Norling [mailto:[EMAIL PROTECTED]]
> > Sent: den 17 oktober 2003 12:19
> > To: 'N. V.'; [EMAIL PROTECTED]
> > Subject: RE: [Nant-users] Logging failures or
successes
> >
>
>
> > Hi Nick.
>
>
> > Thanks for the tip, that's pretty much
exactly what I need!
> > Got to look closer at
things in NAntContrib I guess.
> >
> > /Nicke
> >
> >
> >
-------------------------------------------------------
> > This SF.net email sponsored by: Enterprise Linux Forum
> Conference & Expo
> > The Event For Linux Datacenter Solutions & Strategies in
> The Enterprise
> >
Linux in the Boardroom; in the Front Office; & in the Server Room
> > http://www.enterpriselinuxforum.com
> > _______________________________________________
> > Nant-users mailing list
> > [EMAIL PROTECTED]
>
> https://lists.sourceforge.net/lists/listinfo/nant-users
> >
> >
>
