opensubscriber
   Find in this group all groups
 
Unknown more information…

n : nant-developers@lists.sourceforge.net 20 July 2009 • 7:19PM -0400

[nant-dev] [ nant-Bugs-2824210 ] xmlns specified causes include failure
by SourceForge.net

REPLY TO AUTHOR
 
REPLY TO GROUP






Bugs item #2824210, was opened at 2009-07-20 07:19
Message generated for change (Settings changed) made by dcanning
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=402868&aid=2824210&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.85
Status: Open
Resolution: None
>Priority: 7
Private: No
Submitted By: David (dcanning)
Assigned to: Nobody/Anonymous (nobody)
Summary: xmlns specified causes include failure

Initial Comment:
including the xmlns for nant on the project causes the <include buildfile="..."/> to fail.  

Attached are 2 simple build files, default.build including example2.xml.  with the xmlns specified on the project in the default.build, the build fails, if you remove the xmlns specification the build succeeds

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

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

------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize  
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
nant-developers mailing list
nant-developers@list...
https://lists.sourceforge.net/lists/listinfo/nant-developers

Bookmark with:

Delicious   Digg   reddit   Facebook   StumbleUpon

opensubscriber is not affiliated with the authors of this message nor responsible for its content.