Bugs item #1167694, was opened at 2005-03-21 17:26
Message generated for change (Comment added) made by drieseng
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=402868&aid=1167694&group_id=31650
Category: Tasks
Group: 0.85
Status: Open
Resolution: None
Priority: 5
Submitted By: John Hardin (john_hardin)
Assigned to: Nobody/Anonymous (nobody)
Summary: <solution> task is not detecting compile errors in resgen
Initial Comment:
One of our ccnet-managed automatic builds was failing.
The error message was somewhat misleading, and further
investigation suggests that nant 0.85rc2 is not
detecting compile errors in a <solution> task under
certain circumstances.
Here is an excerpt of the <solution>'s XML log,
building the "CRM" subproject:
<message level="Info">Building 'CRM' [debug] ...</message>
<task name="attrib"/>
<task name="resgen"/>
<task name="resgen"/>
<task name="resgen"/>
<task name="resgen"/>
<task name="resgen"/>
<task name="resgen"/>
<task name="resgen"/>
<task name="resgen"/>
<task name="resgen"/>
<task name="resgen"/>
<task name="resgen"/>
<task name="resgen"/>
<task name="resgen"/>
<message level="Info">
c:\{mumble}\CRM\CreateNotesForm.cs(18,40): error
CS0234: The type or namespace name 'RenderRadioButton'
does not exist in the class or
namespace 'CRS.VisualFramework.WinForms' (are you
missing an assembly reference?)
</message>
<message level="Info">
c:\{mumble}\CRM\CreateNotesForm.cs(19,40): error
CS0234: The type or namespace name 'RenderRadioButton'
does not exist in the class or namespace
'CRS.VisualFramework.WinForms' (are you missing an ssembly
reference?)
</message>
<task name="copy"/>
<task name="copy"/>
<task name="copy"/>
<task name="copy"/>
<task name="copy"/>
<task name="copy"/>
<task name="copy"/>
<task name="copy"/>
<task name="copy"/>
<task name="delete"/>
Note that the compile errors did NOT generate a failed
build. The build failed later in ndoc when the
documentation .xml for the CRM project couldn't be found.
The only odd thing I can see is that the errors appear
to be during "resgen" tasks.
The above is about all the information I can provide -
the errors in our code have been fixed, and I don't
know what to do to provide a minimal repro.
Sorry.
----------------------------------------------------------------------
>Comment By: Gert Driesen (drieseng)
Date: 2005-03-22 07:16
Message:
Logged In: YES
user_id=707851
You can run the build in debug mode:
NAnt.exe -debug -logger:NAnt.Core.XmlLogger -
logfile:log.xml -buildfile:<your buildfile>
----------------------------------------------------------------------
Comment By: John Hardin (john_hardin)
Date: 2005-03-22 00:30
Message:
Logged In: YES
user_id=786519
The build file is pretty big. The part where the <solution>
task lives is dirt simple:
<property name="nant.settings.currentframework"
value="net-1.1"/>
<solution configuration="debug"
solutionfile="${project::get-name()}.sln" />
...as you can see, failonerror is not being set to false.
The build file is common across multiple projects - they
just set the project name and include it. The build process
works properly on all projects except the one doing user
interface stuff, and only when the control developers change
things that break other bits of the UI.
I am not closely involved with that side of things so I
don't know how to approach making a minimal repro example
for this, and I don't know whether the UI people will be
able to make a minimal repro example either. I'll ask.
Is there a more verbose level of nant debug logging I can
enable that will help track down what's wrong? I think I can
get the UI devs to break the build without too much
trouble... :)
----------------------------------------------------------------------
Comment By: Gert Driesen (drieseng)
Date: 2005-03-21 22:52
Message:
Logged In: YES
user_id=707851
John,
Can you attach your build file to this bug report ?
Are you sure that you don't have failonerror set to "false" on
the <solution> task ?
The error messages are not output by resgen, but by csc. Its
just not obvious as we don't use the <csc> task, but instead
execute csc.exe directly.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=402868&aid=1167694&group_id=31650
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers
