On 4/27/2012 at 9:10 AM, Benson Margulies wrote: > 1: Should the Lucene PMC publish maven artifacts at all? > > - There seems to remain a consensus of the community: "Yes".
Not really: consensus means unanimous agreement. The rest of your points, Benson, confuse Maven issues around 3rd party artifacts with project governance issues; I won't address them here. I think action needs to be taken to address Maven's impact on the project. Up till now, the bargain was something like: Maven proponents will take care of Maven issues, and others won't have to care. But the 3.6 release cleanup (thanks very much to Robert Muir, Chris Male, Uwe Schindler and others who did the hard work) stands as an example of what will be continuing issues. Robert's summary on SOLR-3405 is on point: > We still dont have: > > - a way to handle patched dependencies for maven > - a way to handle dependencies that are not in maven > - a packaging system for maven consistent with our other packaging. I want to get Lucene/Solr Maven stuff to the point where non-Maven-proponents don't have anything substantive to complain about. In the past I've worked toward addressing people's concerns about Maven in Lucene/Solr. I plan on continuing to do so. Steve
