On 10/11/07, nicolas de loof <[EMAIL PROTECTED]> wrote: > Warning : This could break existing projects ! > > My project has a dependency on castor-1.0. This one has no POM. > If you povide one, rebuilding my app will introduce new transitive > dependencies that were not expected, and my build will become > non-reproductible. > > Only new release of an artifact can come with a POM.
mmm, that's not the case, you shouldn't made releases of things without poms, you should have contributed one already > > Nico. > > 2007/10/11, Jochen Wiedmann <[EMAIL PROTECTED]>: > > > > On 10/11/07, Carlos Sanchez <[EMAIL PROTECTED]> wrote: > > > > > http://maven.apache.org/guides/mini/guide-maven-evangelism.html > > > > Quoting from that text: > > > > ... unless you provide a pom for it ... > > > > I am ready to do that, at least in the cases that harm me. But how? > > Through the standard upload procedure? <quote>open an issue at JIRA MEV with the relevant information </quote> > > > > Jochen > > > > -- > > Look, that's why there's rules, understand? So that you think before > > you break 'em. > > > > -- (Terry Pratchett, Thief of Time) > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
