Return-Path: Delivered-To: apmail-jakarta-ant-dev-archive@apache.org Received: (qmail 98612 invoked from network); 12 Apr 2002 04:51:48 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 12 Apr 2002 04:51:48 -0000 Received: (qmail 17452 invoked by uid 97); 12 Apr 2002 04:51:56 -0000 Delivered-To: qmlist-jakarta-archive-ant-dev@jakarta.apache.org Received: (qmail 17436 invoked by uid 97); 12 Apr 2002 04:51:55 -0000 Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Ant Developers List" Reply-To: "Ant Developers List" Delivered-To: mailing list ant-dev@jakarta.apache.org Received: (qmail 17425 invoked from network); 12 Apr 2002 04:51:55 -0000 Message-ID: <000501c1e1dd$c0b90ee0$0201a8c0@nordwand> From: "Steve Loughran" To: "ant-dev" Subject: WsdlToDotnet Date: Thu, 11 Apr 2002 21:51:46 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N I have added a new WsdlToDotnet task in the dotnet corner, plus a test which also tests the CSC task (finally!) The tests will only run if csc and wsdl are on the path. I am not sure whether case sensitivity in mean that it will work even if they are on the path, on one of my boxes the availability test isnt finding wsdl even though it is there on the command line...more research needed. For web service hackers out there, there is a task in Apache Axis to go alongside this -currently only a test version which rates as "crude", but I have some diffs there that I want to get into the source. Which raises another little wish of mine for ant 1.5 Can we we put BuildFileTest into ant.jar, so that external libraries can use it to test build files. Or should we keep in private for flexibility, and encourage people to cut and paste it into their own apps, moving into a new package if need be. An alternative might be to write (not now! not now!) a meta task to test a build file that would be cool as then you can write many tasks in pure ant (with conditions and fail) to validate stuff. But it wont fit in with the junit execution model. -steve -- To unsubscribe, e-mail: For additional commands, e-mail: