The only safe solution is not to add a pom at all. Even adding an empty one could potentially cause issues depending on the search order of a user's repos or repo manager.
-----Original Message----- From: nicolas de loof [mailto:[EMAIL PROTECTED] Sent: Saturday, October 27, 2007 4:37 AM To: Maven Developers List Subject: Re: groovy-all 1.0 pom in central repo? I recently discussed such a case with carlos, and suggested a rule to ensure maven builds to be reproductible : never add a POM to artifacts that where published in repo with no meta-data. Another derived rule would be to auto-generate minimal POMs (without dependencies) for all artifacts that miss a POM. Nico. 2007/10/27, Joe Bohn <[EMAIL PROTECTED]>: > > I found http://jira.codehaus.org/browse/MEV-550 > and another linked issue that discuss the problem but there's still > nobody assigned to either issue. > > Any chance the original change can be reverted or perhaps the pom > updated to remove the deps on openejb 1.0? > > Joe > > > Jason Dillon wrote: > > So, who put the groovy-all 1.0 pom in the central repository? > > > > This has *broken* a lot of projects and has made many releases > > unbuildable... > > > > Who did this and why? Anyone know? > > > > --jason > > > > --------------------------------------------------------------------- > 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]
