[nant-dev] [ nant-Bugs-1180135 ] $PATH/bin/monoresgen.exe not found
Bugs item #1180135, was opened at 2005-04-10 10:35 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=402868aid=1180135group_id=31650 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: fabian seoane (fseoane) Assigned to: Nobody/Anonymous (nobody) Summary: $PATH/bin/monoresgen.exe not found Initial Comment: In ubuntu (and i believe that also in debian), nant is using $PATH/bin/monoresgen.exe as resgen tool, but should be using $PATH/bin/monoresgen . The result is a [resgen] cannot open assembly /usr/bin/monoresgen.exe, and a build failure. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=402868aid=1180135group_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=6595alloc_id=14396op=click ___ nant-developers mailing list nant-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-developers
[nant-dev] [ nant-Bugs-1180135 ] $PATH/bin/monoresgen.exe not found
Bugs item #1180135, was opened at 2005-04-10 10:35 Message generated for change (Comment added) made by fseoane You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=402868aid=1180135group_id=31650 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: fabian seoane (fseoane) Assigned to: Nobody/Anonymous (nobody) Summary: $PATH/bin/monoresgen.exe not found Initial Comment: In ubuntu (and i believe that also in debian), nant is using $PATH/bin/monoresgen.exe as resgen tool, but should be using $PATH/bin/monoresgen . The result is a [resgen] cannot open assembly /usr/bin/monoresgen.exe, and a build failure. -- Comment By: fabian seoane (fseoane) Date: 2005-04-10 12:20 Message: Logged In: YES user_id=910443 ooops!, sorry. NAnt: NAnt 0.85 (Build 0.85.1869.0; rc2; 12/02/2005) Mono: 1.0.5 /package from ubuntu 5.04) -- Comment By: Gert Driesen (drieseng) Date: 2005-04-10 11:57 Message: Logged In: YES user_id=707851 What version of Mono and NAnt are you using ? -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=402868aid=1180135group_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=6595alloc_id=14396op=click ___ nant-developers mailing list nant-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-developers
[nant-dev] [ nant-Bugs-1180135 ] $PATH/bin/monoresgen.exe not found
Bugs item #1180135, was opened at 2005-04-10 12:35 Message generated for change (Comment added) made by drieseng You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=402868aid=1180135group_id=31650 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: fabian seoane (fseoane) Assigned to: Nobody/Anonymous (nobody) Summary: $PATH/bin/monoresgen.exe not found Initial Comment: In ubuntu (and i believe that also in debian), nant is using $PATH/bin/monoresgen.exe as resgen tool, but should be using $PATH/bin/monoresgen . The result is a [resgen] cannot open assembly /usr/bin/monoresgen.exe, and a build failure. -- Comment By: Gert Driesen (drieseng) Date: 2005-04-10 16:53 Message: Logged In: YES user_id=707851 We actually don't use the mono shell scripts, but instead execute the assemblies using the mono runtime. I'm pretty sure that in mono 1.0.x all tool assemblies used to be in the $prefix/bin directory. Check you check where all of the following files are located on your system (either in $prefix/bin or $prefix/lib): monoresgen.exe sn.exe al.exe Are they all in the $prefix/lib directory ? -- Comment By: fabian seoane (fseoane) Date: 2005-04-10 14:20 Message: Logged In: YES user_id=910443 ooops!, sorry. NAnt: NAnt 0.85 (Build 0.85.1869.0; rc2; 12/02/2005) Mono: 1.0.5 /package from ubuntu 5.04) -- Comment By: Gert Driesen (drieseng) Date: 2005-04-10 13:57 Message: Logged In: YES user_id=707851 What version of Mono and NAnt are you using ? -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=402868aid=1180135group_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=6595alloc_id=14396op=click ___ nant-developers mailing list nant-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-developers
[nant-dev] [ nant-Bugs-1179497 ] DeleteTask: The directory does not exist. error
Bugs item #1179497, was opened at 2005-04-09 00:02
Message generated for change (Comment added) made by drieseng
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=402868aid=1179497group_id=31650
Category: Tasks
Group: None
Status: Closed
Resolution: Invalid
Priority: 5
Submitted By: Eric Wright (eiw)
Assigned to: Gert Driesen (drieseng)
Summary: DeleteTask: The directory does not exist. error
Initial Comment:
When using the delete task I get the message:
[delete] Cannot delete
directory 'C:\Source\SPP_Admin\SPP\bin'. The
directory does not exist. when infact the directory does
exist. Even though there is an error it still deletes the
directory. Using failonerror avoids failure but I am still
getting garabe in my log.
This only happens for some directories. Here is my
delete tasks, the first one always works while the
second one doesnt.
delete dir=${build.dir}/${project.name}/bin
failonerror=false /
delete dir=${build.dir}/${project.name}/obj
failonerror=false /
and here is my output:
[delete] Deleting
directory 'C:\Source\SPP_Admin\SPPAPI\bin'.
[delete] C:\Source\SPP_Admin\SPPAPI\SPPAPI.build
(60,4):
[delete] Cannot delete
directory 'C:\Source\SPP_Admin\SPPAPI\obj'. The
directory does not exist.
I also tried adding an 'if=' to the task and that doesnt
change anything. I tried using the if task as well and
here are those results:
[echo] Directory C:\Source\SPP_Admin/Navigation/obj
exists
[delete]
C:\Source\SPP_Admin\Navigation\Navigation.build(61,5):
[delete] Cannot delete
directory 'C:\Source\SPP_Admin\Navigation\obj'. The
directory does not exist.
[echo] Directory C:\Source\SPP_Admin/Navigation/bin
exists
[delete] Deleting
directory 'C:\Source\SPP_Admin\Navigation\bin'.
and here are the if tasks:
if test=${not directory::exists('${build.dir}/
${project.name}/obj')}
echo message=Directory ${build.dir}/
${project.name}/obj exists /
delete dir=${build.dir}/${project.name}/obj
failonerror=false /
/if
if test=${not directory::exists('${build.dir}/
${project.name}/bin')}
echo message=Directory ${build.dir}/
${project.name}/bin exists /
delete dir=${build.dir}/${project.name}/bin
failonerror=false /
/if
--
Comment By: Gert Driesen (drieseng)
Date: 2005-04-10 17:29
Message:
Logged In: YES
user_id=707851
The logic of your if tasks does not seem correct: you're
only removing directories if they do not exist.
Also, in function calls you don't need to enclose property
names in ${..}.
Try using this:
delete dir=${build.dir}/${project.name}/bin
if=${directory::exists(build.dir + '/' + project.name + '/bin')} /
I for one think that behaviour of the delete task sucks: it
should not fail if the directory that you're trying to delete does
not exist.
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=402868aid=1179497group_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=6595alloc_id=14396op=click
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers
[nant-dev] [ nant-Bugs-1167694 ] solution task is not detecting compile errors in resgen
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=detailatid=402868aid=1167694group_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=InfoBuilding '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-04-10 18:03
Message:
Logged In: YES
user_id=707851
Ping!
--
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=detailatid=402868aid=1167694group_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=6595alloc_id=14396op=click
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers
[nant-dev] [ nant-Bugs-1164591 ] nunit2 dies using plain formatter if all tests are explicit
Bugs item #1164591, was opened at 2005-03-16 17:28 Message generated for change (Comment added) made by drieseng You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=402868aid=1164591group_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: nunit2 dies using plain formatter if all tests are explicit Initial Comment: nant-0.85rc2 If a unit test .dll has tests, but all the tests are explicit, and the nunit2 task is run with the Plain formatter, the nunit2 task dies with System.Xml.XmlException. If the formatter is Xml the nunit2 task does not die. Adding a single dummy (always successful) unit test to the test fixture corrects the problem. failure - builderror typeNAnt.Core.BuildException/type messageTest results could not be formatted./message - location - filename c:\buildbot\devel\csharp\applications\CRS\standard-build.include /filename linenumber83/linenumber columnnumber6/columnnumber /location - stacktrace at NAnt.NUnit2.Tasks.NUnit2Task.FormatResult(NUnit2Test testElement, TestResult result) at NAnt.NUnit2.Tasks.NUnit2Task.ExecuteTask() at NAnt.Core.Task.Execute() at NAnt.Core.TaskContainer.ExecuteChildTasks() at NAnt.Core.TaskContainer.ExecuteTask() at NAnt.Core.Task.Execute() at NAnt.Core.Tasks.LoopTask.ExecuteChildTasks() at NAnt.Core.Tasks.LoopTask.DoWork(String[] propVals) at NAnt.Core.Tasks.LoopTask.ExecuteTask() at NAnt.Core.Task.Execute() at NAnt.Core.Target.Execute() at NAnt.Core.Project.Execute(String targetName, Boolean forceDependencies) at NAnt.Core.Project.Execute() at NAnt.Core.Project.Run() /stacktrace - internalerror typeSystem.Xml.XmlException/type - message An unexpected end of file parsing CDATA has occurred. Line 417, position 51. /message - stacktrace at System.Xml.XmlScanner.ScanCData() at System.Xml.XmlScanner.ScanMarkup() at System.Xml.XmlTextReader.ParseTag() at System.Xml.XmlTextReader.ParseBeginTagExpandCharEntities() at System.Xml.XmlTextReader.Read() at System.Xml.XmlValidatingReader.ReadNoCollectTextToken() at System.Xml.XmlValidatingReader.Read() at System.Xml.XPath.XPathDocument.ReadChildNodes(XPathContainer parent, String parentBaseUri, XmlReader reader, PositionInfo positionInfo) at System.Xml.XPath.XPathDocument.ReadChildNodes(XPathContainer parent, String parentBaseUri, XmlReader reader, PositionInfo positionInfo) at System.Xml.XPath.XPathDocument.ReadChildNodes(XPathContainer parent, String parentBaseUri, XmlReader reader, PositionInfo positionInfo) at System.Xml.XPath.XPathDocument.ReadChildNodes(XPathContainer parent, String parentBaseUri, XmlReader reader, PositionInfo positionInfo) at System.Xml.XPath.XPathDocument.ReadChildNodes(XPathContainer parent, String parentBaseUri, XmlReader reader, PositionInfo positionInfo) at System.Xml.XPath.XPathDocument.ReadChildNodes(XPathContainer parent, String parentBaseUri, XmlReader reader, PositionInfo positionInfo) at System.Xml.XPath.XPathDocument.ReadChildNodes(XPathContainer parent, String parentBaseUri, XmlReader reader, PositionInfo positionInfo) at System.Xml.XPath.XPathDocument.ReadChildNodes(XPathContainer parent, String parentBaseUri, XmlReader reader, PositionInfo positionInfo) at System.Xml.XPath.XPathDocument.ReadChildNodes(XPathContainer parent, String parentBaseUri, XmlReader reader, PositionInfo positionInfo) at System.Xml.XPath.XPathDocument.ReadChildNodes(XPathContainer parent, String parentBaseUri, XmlReader reader, PositionInfo positionInfo) at System.Xml.XPath.XPathDocument.ReadChildNodes(XPathContainer parent, String parentBaseUri, XmlReader reader, PositionInfo positionInfo) at System.Xml.XPath.XPathDocument.ReadChildNodes(XPathContainer parent, String parentBaseUri, XmlReader reader, PositionInfo positionInfo) at System.Xml.XPath.XPathDocument.ReadChildNodes(XPathContainer parent, String parentBaseUri, XmlReader reader, PositionInfo positionInfo) at System.Xml.XPath.XPathDocument.ReadChildNodes(XPathContainer parent, String parentBaseUri, XmlReader reader, PositionInfo positionInfo) at System.Xml.XPath.XPathDocument.ReadChildNodes(XPathContainer parent, String parentBaseUri, XmlReader reader, PositionInfo positionInfo) at System.Xml.XPath.XPathDocument.ReadChildNodes(XPathContainer parent, String parentBaseUri, XmlReader reader, PositionInfo positionInfo) at System.Xml.XPath.XPathDocument.ReadChildNodes(XPathContainer parent, String parentBaseUri, XmlReader reader, PositionInfo positionInfo) at System.Xml.XPath.XPathDocument.ReadChildNodes(XPathContainer parent, String parentBaseUri, XmlReader reader, PositionInfo positionInfo) at System.Xml.XPath.XPathDocument.ReadChildNodes(XPathContainer parent, String parentBaseUri, XmlReader reader, PositionInfo positionInfo) at
[nant-dev] [ nant-Bugs-1117795 ] Solution task can't handle trailing \ on include dirs
Bugs item #1117795, was opened at 2005-02-07 11:40 Message generated for change (Comment added) made by drieseng You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=402868aid=1117795group_id=31650 Category: Tasks Group: 0.85 Status: Closed Resolution: Out of Date Priority: 5 Submitted By: Philip Craig (philipcraig) Assigned to: Gert Driesen (drieseng) Summary: Solution task can't handle trailing \ on include dirs Initial Comment: The Solution dir fails to find include files in a c++ solution if the Include directories in the project have a trailing \. -- Comment By: Gert Driesen (drieseng) Date: 2005-04-10 18:04 Message: Logged In: YES user_id=707851 This should be fixed in recent nightly build. I'm closing this because of lack of feedback -- Comment By: Gert Driesen (drieseng) Date: 2005-03-12 13:41 Message: Logged In: YES user_id=707851 Ping! -- Comment By: Gert Driesen (drieseng) Date: 2005-02-26 09:55 Message: Logged In: YES user_id=707851 Can you verify whether you still run into this issue with the next nightly build ? -- Comment By: Gert Driesen (drieseng) Date: 2005-02-09 06:21 Message: Logged In: YES user_id=707851 ping ! -- Comment By: Gert Driesen (drieseng) Date: 2005-02-07 11:48 Message: Logged In: YES user_id=707851 This issue should definitely be fixed in recent nightly builds. Can you try this ? -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=402868aid=1117795group_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=6595alloc_id=14396op=click ___ nant-developers mailing list nant-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-developers
[nant-dev] [ nant-Bugs-1170554 ] nant does not work under Windows XP Pro 64bit
Bugs item #1170554, was opened at 2005-03-25 15:55 Message generated for change (Comment added) made by drieseng You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=402868aid=1170554group_id=31650 Category: Core Group: 0.85 Status: Open Resolution: None Priority: 5 Submitted By: Rodrigo B. de Oliveira (rodrigobamboo) Assigned to: Nobody/Anonymous (nobody) Summary: nant does not work under Windows XP Pro 64bit Initial Comment: I've just tried both the latest stable and nightly build but they fail to recognized the .net framework 2.0 beta 1 64bit. -- Comment By: Gert Driesen (drieseng) Date: 2005-04-10 18:06 Message: Logged In: YES user_id=707851 Any progress to report ? Do you want me to take a look (using VNC) ? -- Comment By: Rodrigo B. de Oliveira (rodrigobamboo) Date: 2005-03-25 18:34 Message: Logged In: YES user_id=605269 Yep. The AMD64 version. -- Comment By: Gert Driesen (drieseng) Date: 2005-03-25 18:27 Message: Logged In: YES user_id=707851 Hmm, strange that you had to add that key manually. Did you actually install the .NET SDK ? -- Comment By: Rodrigo B. de Oliveira (rodrigobamboo) Date: 2005-03-25 18:09 Message: Logged In: YES user_id=605269 After manually adding the SOFTWARE\Microsoft\.NETFramework\sdkInstallRootv2.0 string value to the registry the framework is now recognized. I'm getting Invalid Command Line Syntax errors with resgen but that should be easy to fix... Let's see. -- Comment By: Rodrigo B. de Oliveira (rodrigobamboo) Date: 2005-03-25 16:49 Message: Logged In: YES user_id=605269 I thought that maybe the debug log could tell you something... But hey Gert, we can try a VNC session later if you are in the mood. -- Comment By: Gert Driesen (drieseng) Date: 2005-03-25 16:09 Message: Logged In: YES user_id=707851 If you can provide me a 64bit box, I'd be glad to look into it ;-) -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=402868aid=1170554group_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=6595alloc_id=14396op=click ___ nant-developers mailing list nant-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-developers
[nant-dev] [ nant-Bugs-1172644 ] solution task no longer creates .xml documentation files
Bugs item #1172644, was opened at 2005-03-29 18:51 Message generated for change (Comment added) made by drieseng You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=402868aid=1172644group_id=31650 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Corbin Hoenes (crowcomputer) Assigned to: Nobody/Anonymous (nobody) Summary: solution task no longer creates .xml documentation files Initial Comment: In NAnt 0.85-rc1 I was able to have the DocumentationFile attribute of Build/Settings/Config element in the .csproj file. Now in 0.85-rc2 I get the error that the [documentation file name].xml file cannot be copied. I assume it's coping the documentation file to the output directory after it's generated but isn't being generated anymore. -- Comment By: Gert Driesen (drieseng) Date: 2005-04-10 18:07 Message: Logged In: YES user_id=707851 Ping ! -- Comment By: Gert Driesen (drieseng) Date: 2005-03-29 20:33 Message: Logged In: YES user_id=707851 Corbin, I cannot reproduce this issue here. Can you attach a small repro to this bug report ? Thanks ! -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=402868aid=1172644group_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=6595alloc_id=14396op=click ___ nant-developers mailing list nant-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-developers
