Please post the POM, so we can have a look ^_^ - Yann
2006/8/31, Douglas Ferguson <[EMAIL PROTECTED]>:
By the way, if I wan to flesh out these skeletan pom files to get rid of the error, what do I need to do? The error just says it doesn't validate, but I don't really see anything wrong with the pom. D- ----- Original Message ----- From: [EMAIL PROTECTED] Sent: Wed, 8/30/2006 10:01pm To: users Subject: RE: pom files not validating Yeah.. I already have a 3rd party branch. I just didn't realize that it would barf at me cuz the pom was skeletal. Some of this stuff doesn't even have a pom, i.e. some weird library from a partner, etc. -----Original Message----- From: Mykel Alvis [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 30, 2006 4:21 PM To: Maven Users List Subject: Re: pom files not validating My $0.02: I used to do this, but I've since decided that it's worth the time to take the generated POM from the maven deploy, go back to the projects (where I'm able to), and update the POM to make it into a "real" POM instead of a skeletal one. I ended up with a large number of dependencies in projects that were essentially transitive, but had to be included at the base level because they were transitive to 3rd party dependencies, not to our actual project. I wish people who packaged deployments to central would do this more often. I also suggest making sure that you separate your internal repository from your [internally-deployed EXTERNAL/3rd party] repository. It's made a lot of difference since I could make one of my ongoing tasks into "look for public repositories for the 3rd party jars", such as when java-dev-net made the javax libs available. On 8/30/06, Douglas Ferguson <[EMAIL PROTECTED]> wrote: > > 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] > > -- I'm just an unfrozen caveman software developer. I don't understand your strange, "modern" ways. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
