[ nant-Bugs-3008782 ] output still all in one line

Bugs item #3008782, was opened at 2010-05-28 15:04
Message generated for change (Comment added) made by rmboggs
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=402868&aid=3008782&group_id=31650

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Core
Group: 0.90
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: http://duncanmcrae.myopenid.com ()
Assigned to: Nobody/Anonymous (nobody)
Summary: output still all in one line

Initial Comment:
nant-0.91-nightly-2010-05-12

I use the build output for debugging, and it gets picked up by CC.NET.  At least to me, it is important that this be legible, so I'm really looking forward to this getting resolved (and released in a nightly build).  Thanks!



###looks good - begin

    convert.sqlTemplate:
    
    [loadtasks] Scanning assembly "NAnt.Contrib.Tasks" for extensions.
         [copy] Copying 1 file to 'C:\development\ServerMonitor\trunk\database.copy.build.number'.
      [version] Build number '0.0.1.0'.
         [copy] Copying 1 file to 'C:\development\ServerMonitor\trunk\source\tsql\build.sql'.
    
###looks good - end
###nightmare to read - begin
         [exec] ####################################################################################################BUILD 00001 - DEBUT####################################################################################################Changed database context to 'ServerMonitor'.Changed database context to 'master'. ServerMonitor - debut    drop database ServerMonitor - debut    drop database ServerMonitor - finis    create database ServerMonitor - debut    create database ServerMonitor - finis    set properties ServerMonitor - debutDBCC execution completed. If DBCC printed error messages, contact your system administrator.    set properties ServerMonitor - finisChanged database context to 'ServerMonitor'. dbo.t_DiscSpaceFree - debutdbo.t_DiscSpaceFree - finis dbo.t_log_action - debutdbo.t_
 log_action - finis dbo.t_log_error - debutdbo.t_log_error - finis dbo.t_log_error_elmah - debut    create table dbo.t_log_error_elmah - debut    create table dbo.t_log_error_elmah - finisdbo.t_log_error_elmah - finis dbo.proc_DiscSpaceFree_PollServer - debut    create procedure dbo.proc_DiscSpaceFree_PollServer - debutCannot add rows to sys.sql_dependencies for the stored procedure because it depends on the missing table 'dbo.proc_log_action_simple'. The stored procedure will still be created; however, it cannot be successfully executed until the table exists.Cannot add rows to sys.sql_dependencies for the stored procedure because it depends on the missing table 'dbo.proc_log_generateParameterString'. The stored procedure will still be created; however, it cannot be successfully executed
  until the table exists.Cannot add rows to sys.sql_dependencies for the stored procedure because it depends on the missing table 'dbo.proc_log_action_verbose'. The stored procedure will still be created; however, it cannot be successfully executed until the table exists.Cannot add rows to sys.sql_dependencies for the stored procedure because it depends on the missing table 'dbo.proc_log_error'. The stored procedure will still be created; however, it cannot be successfully executed until the table exists.    create procedure dbo.proc_DiscSpaceFree_PollServer - finisdbo.proc_DiscSpaceFree_PollServer - finis dbo.proc_log_action_simple - debut    create procedure dbo.proc_log_action_simple - debutCannot add rows to sys.sql_dependencies for the stored procedure because it depends on the missi
 ng table 'dbo.proc_log_error'. The stored procedure will still be created; however, it cannot be successfully executed until the table exists.    create procedure dbo.proc_log_action_simple - finisdbo.proc_log_action_simple - finis dbo.proc_log_action_verbose - debut    create procedure dbo.proc_log_action_verbose - debutCannot add rows to sys.sql_dependencies for the stored procedure because it depends on the missing table 'dbo.proc_log_error'. The stored procedure will still be created; however, it cannot be successfully executed until the table exists.    create procedure dbo.proc_log_action_verbose - finisdbo.proc_log_action_verbose - finis dbo.proc_log_error - debut    create procedure dbo.proc_log_error - debut    create procedure dbo.proc_log_error - finisdbo.proc_log_error - fini
 s dbo.proc_log_generateParameterString - debut    create procedure dbo.proc_log_generateParameterString - debut    create procedure dbo.proc_log_generateParameterString - finisdbo.proc_log_generateParameterString - finis####################################################################################################BUILD 00001 - FINIS####################################################################################################

###nightmare to read - end


----------------------------------------------------------------------

>Comment By: Ryan Boggs (rmboggs)
Date: 2010-09-20 16:33

Message:
Were you able to create a sanitized build file for us to test?

----------------------------------------------------------------------

Comment By: Ryan Boggs (rmboggs)
Date: 2010-08-13 13:45

Message:
There is no formal install but the executables are usually copied to a
specific directory that is in the system path so it can be called in the
command prompt.  If you have more than one version of NAnt on your hard
drive, it could be possible that the wrong one is called resulting in this
old bug.  I'm not saying that this is the reason for the error but it
should be explored before going further.

Also, do you have that sample build file available I can use?

----------------------------------------------------------------------

Comment By: http://duncanmcrae.myopenid.com ()
Date: 2010-07-18 12:19

Message:
I am not sure I ever "installed" NAnt, I believe I have always referenced
the executable directly.  I can check that out on Monday, as well as post a
sanitised version of my .build file.

You are correct that I am calling sqlcmd.exe in the EXEC task.

----------------------------------------------------------------------

Comment By: Ryan Boggs (rmboggs)
Date: 2010-07-18 10:48

Message:
You can post your build as an attachment to this bug report.  I have no
problem with that as long as it doesn't contain any sensitive information
that shouldn't be shared.

Looking at your snippets below, it looks like you are calling the MS SQL
Server command line program via NAnt's Exec command?  Is that correct?  If
so, I can use that as a  starting point.

Just out of curiosity, have you tried doing a clean install (as in
removing the previous version of NAnt before installing the latest
version)?  I know there was a bug or two that was recently solved by doing
that.  If you haven't tried that, I would say to give that a go.

----------------------------------------------------------------------

Comment By: http://duncanmcrae.myopenid.com ()
Date: 2010-07-16 11:56

Message:
I was going to post my .BUILD, but decided that might be a little
obnoxious.  Before doing so I can point out that I have a target which
includes the EXEC task:

<exec program="${sqlcmd.exe}" commandline="${sqlcmd.ConnectionString} -b
-i ${filename}" />

I have reverted to the earlier release of NAnt, I'll upgrade to your
latest nightly release next week.

Thank you for staying on this (the bug AND the project).  After a day or
two of using NAnt *I* was sold, but I was uncomfortable pushing it with
clients when it hadn't been updated in what, two years?  Anyway, I am happy
to know that someone is keeping this tool alive.

----------------------------------------------------------------------

Comment By: Ryan Boggs (rmboggs)
Date: 2010-07-15 22:28

Message:
I am not sure why you are still experiencing this error, I haven't seen
this issue since 0.90 release.  What task(s) are you running that is
causing this issue?

I ran a new nightly that has some updates, though not directly addressing
this.  I would say give it a go just to see if it is any better.

----------------------------------------------------------------------

Comment By: http://duncanmcrae.myopenid.com ()
Date: 2010-07-15 08:44

Message:
My bad:  nant-0.91-nightly-2010-05-12 is still the latest available nightly
release.

What is my next step to help you?


----------------------------------------------------------------------

Comment By: http://duncanmcrae.myopenid.com ()
Date: 2010-07-15 08:15

Message:
Sorry it has taken me so long to respond.

I have two projects, both of which use the same build of NAntContrib: 
nantcontrib-0.86-nightly-2009-02-01

When I build using nant-0.86-nightly-2009-05-05, I get what I am
expecting, lots of different lines.  When I build using
nant-0.91-nightly-2010-05-12, everything is on one line.  I will now
download the latest nightly build and respond again.


----------------------------------------------------------------------

Comment By: Ryan Boggs (rmboggs)
Date: 2010-07-03 21:09

Message:
I think that this may have been fixed by 0.90 Final.  Unless anyone else
can verify that this is still an outstanding issue, I'm going to close it
before 0.91 Alpha2.

----------------------------------------------------------------------

Comment By: Ryan Boggs (rmboggs)
Date: 2010-05-28 15:31

Message:
What version of NAntContrib are you using?
Do you have a sample script we can use to test?
Have your reported this issue to NAntContrib?

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=402868&aid=3008782&group_id=31650

------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev