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-SNAPSH OT, Failed Path Check = C:\workspace\npanday\target\NPanday.Model.Pom.dll 12-Dec-2011 14:27:51 npanday.dao.impl.ProjectDaoImpl storeProjectAndResolveDepen Dencies
All of those dlls *DO* exist in my /target folder. It "succeeds", but still no npanday-settings.xml file. Thanks, -Alan- -----Original Message----- From: Lars Corneliussen [mailto:m...@lcorneliussen.de] Sent: 12 December 2011 12:35 To: npanday-dev@incubator.apache.org Subject: Re: Unable to build Hi, It should be generated in the initialize-phase: NPanday.Plugin.Settings.JavaBinding:1.5.0-azuresupport-SNAPSHOT:generate-settings (default-generate-settings) If you run with "mvn initialize -X" you should see some log output you could share with us. We have plans on totally omiting the generated settings-file for future versions - but that's not today, unfortunately. _ Lars Am 12.12.2011 um 09:56 schrieb Baldwin, Alan (Pfaeffikon): > At what point should the npanday-settings.xml file be written to my ~/.m2 > folder? During install of the npanday msi file? During a build of the > source? > > It's not being generated during either of those steps. My repo is now in the > default location. > > Regards, > > -Alan- > > -----Original Message----- > From: Baldwin, Alan (Pfaeffikon) [mailto:alan.bald...@man.com] > Sent: 12 December 2011 08:44 > To: npanday-dev@incubator.apache.org > Subject: RE: Unable to build > > Sorry all for the spam. Something must have been misbehaving with our mail > servers. I didn't intend to send the message three times. > > Thanks Lars for the answer. I had been using a custom repository location > since my ~/.m2 folder is on a network share because of a roaming profile. > I'll change it back to the default and see how I get on. > > -Alan- > > -----Original Message----- > From: Lars Corneliussen [mailto:m...@lcorneliussen.de] > Sent: 10 December 2011 17:30 > To: npanday-dev@incubator.apache.org > Subject: Re: Unable to build > > Hi Alan, > > sorry to answer that later. > > 1.4.0-incubating does not support a custom local repository path. It > uses the setting inconsequently and still tries to generate an > npanday-settings.xml-file in ~/.m2 > > Brett Porter has fixed this (according to > https://issues.apache.org/jira/browse/NPANDAY-284) for > 1.4.1-incubating-SNAPSHOT, which you can retrieve from here: > > http://vmbuild.apache.org/archiva/repository/npanday-snapshots > > 1.4.1-incubating will be released shortly. > > _ > Lars > > Am 09.12.2011 um 14:37 schrieb Baldwin, Alan (Pfaeffikon): > >> Hi all, >> I'm trying to build Npanday from source and getting the following error. >> I'm running 'mvn clean install' >> >> I believe it to be caused by a missing npanday-settings.xml file which is >> then unable to resolve the path of the .net framework sdk. I have a custom >> local repository location at c:\maven. However, >> https://issues.apache.org/jira/browse/NPANDAY-361 indicates that this is >> possible. >> >> >> [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. >> >> I followed the instructions here: >> http://incubator.apache.org/npanday/docs/1.4.0-incubating/developers/ >> i >> ndex.html >> >> Any ideas? >> >> Regards, >> >> -Alan- >> >> 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 >> >
