if one set of users never see them, why should everyone else? -- dims
On Tue, Jul 8, 2008 at 8:18 AM, Bertrand Delacretaz <[EMAIL PROTECTED]> wrote: > On Tue, Jul 8, 2008 at 1:56 PM, Davanum Srinivas <[EMAIL PROTECTED]> wrote: >> ...Ok. Next we get rid of disclaimers everywhere? What purpose does that >> serve?... > > I don't see why we would get rid of disclaimers. > -Bertrand > >> >> Bertrand Delacretaz wrote: >> | Hi Dims, >> | >> | On Tue, Jul 8, 2008 at 12:25 PM, Davanum Srinivas <[EMAIL PROTECTED]> >> wrote: >> | >> |> ...Any PMC that ships incubator developed code is responsible for what >> |> happens when a community does not form around the code base used. Any >> |> one outside Apache that ships incubator code should be totally aware >> |> of what they are getting into.... >> | >> | Agreed. >> | >> |> ...Bottom line, who ever used abdera code should do it consciously. I >> |> agree that adding a second repo may be causing pain to the end users. >> |> But this is for better or worse a "feature" because we don't have a >> |> better way of doing this given the tools we have and the use cases the >> |> tools are pushing on unsuspecting users :)... >> | >> | It might be a feature when someone has add the incubating repository >> | to their configs the first time they need it, but after that any >> | incubating artifacts might sneak in without people noticing it. People >> | will add the incubating repository to their parent poms, and it will >> | be mostly invisible after that. >> | >> |> ...So can we figure out another way to make the end user make a conscious >> |> decision?... >> | >> | The final solution to this probably belongs in Maven, where the >> | general case of "I want to approve any transitive dependency >> | explicitely" should be solved. I'm not following Maven enough to know >> | if that's on their todo list. >> | >> |> ...I doubt we will get much help from the maven team to support this use >> |> case. They would rather get the central repo and get it done! What >> |> bugs me is that in this whole discussion, no one even mentions how >> |> easy it is to add another repo in the poms or the settings.... >> | >> | I agree that it is easy, but as explained above it probably only >> | solves a small part of the problem, and some of us think that that's >> | not worth the hassle. Add on top of that the varying perception of the >> | quality and "Apacheness" of incubator releases, and you get the whole >> | range of opinions about a separate repository, which we're seeing in >> | this and other discussions. >> | >> |> ...Why can't people at least pretend to come up with some alternatives >> |> rather than just chant "central repo!" :)... >> | >> | The central repository is very useful for Maven users, so I guess we >> | want it to be as complete as possible. >> | >> | -Bertrand >> | >> | --------------------------------------------------------------------- >> | To unsubscribe, e-mail: [EMAIL PROTECTED] >> | For additional commands, e-mail: [EMAIL PROTECTED] >> | >> -----BEGIN PGP SIGNATURE----- >> Version: GnuPG v1.4.6 (GNU/Linux) >> >> iD8DBQFIc1XzgNg6eWEDv1kRAhvcAKCPrbUsWR7hM70VHOIzzdI3mvtO2ACeObL4 >> r3vI/cKBW5IPBcbUK01PwvA= >> =NCss >> -----END PGP SIGNATURE----- >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > > > -- > Bertrand Delacretaz > http://www.codeconsult.ch > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Davanum Srinivas :: http://davanum.wordpress.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
