In that case I think the warning about a missing POM needs to be stronger and make people aware of the implications of someone suddenly uploading one.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Carlos Sanchez Sent: Tuesday, 16 October 2007 8:22 AM To: Maven Developers List Subject: [***POSSIBLE SPAM***] - Re: Fix missing POM files - Email has different SMTP TO: and MIME TO: fields in the email addresses i don't agree, the point of not having a pom there is to be able to add one later with the right info. If you work against something without pom, hey, it's your decision, but you are aware that it's a problem, as all the warnings tell you On 10/15/07, William Ferguson <[EMAIL PROTECTED]> wrote: > Isn't the goal here to stop incessant warnings during a build about > trying to downalod a missing POM? > > The way to do that is to that is to upload a POM for that artifact to > the repository. > > But Nico is right is that the uploaded POM should not break existing > builds. Which means that the POM just needs to be bare bones and list > no dependencies as the missing POM introduces no deps. > > So Nico, I'd suggest you create a simple POM with just groupId, > artifactId and version and get it uploaded to the repository. > > Can I also suggest that it is a worthy task to auto generate and > upload such POMs for all artifacts in central with a missing POM. > > William --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
