lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Benson Margulies <>
Subject Re: [DISCUSS] Build/deploy Maven artifacts outside of Lucene/Solr
Date Mon, 23 Apr 2012 19:23:58 GMT
On Mon, Apr 23, 2012 at 3:09 PM, Robert Muir <> wrote:
> On Mon, Apr 23, 2012 at 3:02 PM, Benson Margulies <> wrote:
>> That's right. If you, Rob Muir, just so happen to set up a github
>> project with a fix to Xerces, and I, Benson Margulies, just happen to
>> help you publish it to Maven Central, then the PMC, without (much)
>> fear of hassle, can consume it as a binary dependency. But some folks
>> will want to be sure that we have drawn a bright line between this
>> process and the formal activities of the PMC.
> They may want that: but that doesn't mean they will get it.
> Personally I'm pretty frustrated at the insinuation that anything we
> did for 3.6 is questionable, we spent a shitload of time trying to
> make sure there was no .jar files in source release, no fake maven
> releases of other peoples code, no sketchy links to anything on apache
> infra, or anything like that.
> Seeing that I (and a bunch of other people) stayed up for many long
> nighters to clean this crap up, I'm willing to stand up for it: so
> like I said I have no concerns at all.
> If anyone in the PMC is concerned with how the dependencies for 3.6
> were managed in that release, then speak your mind. But nobody voted
> against it so I can only hope that you have a minority opinion here.

Rob, did you mean 'Benson' by 'you' in that sentence? If so, I'm
really sorry if I've given you the impression I think that that
there's anything amiss with 3.6.0. All I meant to say was that, over
the long haul, if the PMC was very obviously using the dev list to
plan, manage, and execute many things like what you did with Jetty,
someone might criticize.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message