I deployed them with mvn deploy:deploy-file. I had previously used mvn install:install-file and then copied them from there to the internal repository, but there where no poms. So I then ran mvn deploy:deploy-file.
I let maven generate the poms. -----Original Message----- From: Yann Le Du [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 30, 2006 1:51 PM To: Maven Users List Subject: Re: pom files not validating How did you deploy your 3rd party library ? With mvn install:install-file ? Then, did you use the generatePom option or did you write the POM yourself ? - Yann 2006/8/30, Douglas Ferguson <[EMAIL PROTECTED]>: > > I have some 3rd party library dependencies that aren't in central so I > deployed them to our internal repository. > > > > Whenever I build a project that depends on one of these libraries I get > the following message. > > > > What can I do to get stop this? > > > > [WARNING] POM for 'uk.co.demon.windsong:crypt:pom:0.0.1:provided' is > invalid. It will be ignored for > > artifact resolution. Reason: Failed to validate POM > > > > I tried deleting the pom but then it tries to go out and find it. I'd > like to speed up the build by have the poms available. > > > > D- > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
