OK, so possibly the missing settings file is a red herring. The original email I sent on Friday lists the problem I'm having when I run 'mvn clean install'.
In short, I get the following... Snip... [WARNING] NPANDAY-102-001: No NPanday settings available. Using Defaults. [INFO] NPANDAY-066-016: Did not find executable path, will try system path [WARNING] NPANDAY-070-004: Did not find path for xsd in [] [INFO] 'xsd' is not recognized as an internal or external command, [INFO] operable program or batch file. [WARNING] NPANDAY-070-004: Did not find path for xsd in [] ... ...more stuff ... [ERROR] Failed to execute goal org.apache.npanday.plugins:maven-xsd-plugin:1.4.0 -incubating:xsd (default) on project NPanday.Model.Pom: NPANDAY-1400-000: Unable to execute xsd: Vendor null, frameworkVersion = 2.0.50727, Profile = XSD:SCHEMA Notice that above the Vendor is set to null. I assume this is a symptom of not being able to resolve the path to the framework. /snip... -Alan- -----Original Message----- From: Brett Porter [mailto:br...@porterclan.net] On Behalf Of Brett Porter Sent: 12 December 2011 16:21 To: npanday-dev@incubator.apache.org Subject: Re: Unable to build On 13/12/2011, at 12:32 AM, Baldwin, Alan (Pfaeffikon) wrote: > I get a lot of these warnings when I run 'mvn initialize': > > WARNING: NPANDAY-180-018: Not found in local repository, now > retrieving artifact from wagon:NUnit:NUnit.Framework:library:2.2.8.0, > Failed Path Check = C:\worksp ace\npanday\target\NUnit.Framework.dll > 12-Dec-2011 14:27:51 npanday.dao.impl.ProjectDaoImpl > storeProjectAndResolveDepen dencies > WARNING: NPANDAY-180-018: Not found in local repository, now > retrieving artifact from > wagon:org.apache.npanday:NPanday.Model.AutomationExtensibility:library > :1.4 .1-incubating-SNAPSHOT, Failed Path Check = > C:\workspace\npanday\target\NPanday. > Model.AutomationExtensibility.dll > 12-Dec-2011 14:27:51 npanday.dao.impl.ProjectDaoImpl > storeProjectAndResolveDepen dencies > WARNING: NPANDAY-180-018: Not found in local repository, now > retrieving artifact from > wagon:org.apache.npanday:NPanday.Model.Pom:library:1.4.1-incubating-SN > APSH OT, Failed Path Check = > C:\workspace\npanday\target\NPanday.Model.Pom.dll > 12-Dec-2011 14:27:51 npanday.dao.impl.ProjectDaoImpl > storeProjectAndResolveDepen Dencies That's something wrong with my most recent changes - already have a note here to clean it up. > > All of those dlls *DO* exist in my /target folder. > > It "succeeds", but still no npanday-settings.xml file. I never get an npanday-settings.xml either, I think because my PATH is already correct. Do you have other problems in the build? - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter http://twitter.com/brettporter This email has been sent by a member of the Man group (“Man”). Man’s parent company, Man Group plc, is registered in England and Wales (company number 2921462) at Riverbank House, 2 Swan Lane, London, EC4R 3AD. The contents of this email are for the named addressee(s) only. It contains information which may be confidential and privileged. If you are not the intended recipient, please notify the sender immediately, destroy this email and any attachments and do not otherwise disclose or use them. Email transmission is not a secure method of communication and Man cannot accept responsibility for the completeness or accuracy of this email or any attachments. Whilst Man makes every effort to keep its network free from viruses, it does not accept responsibility for any computer virus which might be transferred by way of this email or any attachments. This email does not constitute a request, offer, recommendation or solicitation of any kind to buy, subscribe, sell or redeem any investment instruments or to perform other such transactions of any kind. Man reserves the right to monitor, record and retain all electronic and telephone communications through its network in accordance with applicable laws and regulations. --UwQe9f5k7pI3vplngP
