On Wed, Sep 22, 2010 at 8:47 AM, Grant Ingersoll <[email protected]>wrote:
> > Does an Indic Analyzer have to be part of the release? I have no need for > it and it is optional for a lot (likely most) of people. It's a pain for me > as I have no way of knowing that it is really working b/c I don't speak the > language. Besides, I don't know if the Unit Tests are comprehensive so > there could be things broken in it. Can I choose to not include it if I am > the RM? Same goes for Armenian and all of the other languages I don't > speak. Same goes for the Berkeley DB stuff, the Surround Query Parser, > Instantiated Index and a whole slew of other "features" we release that I, > as an RM, have no use for. My life as an RM would be a whole lot easier if > I simply packaged up core and Solr as source and put them up for download. > Heck, why bother releasing the docs? Some of it isn't always correct and I > don't have a way to test that automatically either. Shall I continue? > your comparison has some flaws, while its true there are likely bugs in all this stuff (and the tests are not 100%), they do in fact have tests. for the javadocs, it too has tests. when you run the javadocs target, it verifies several things: and at the end outputs warnings and errors. maven has nothing. > > Again, for the 5th or 6th time, this is why I said the onus is on those who > want Maven to fix it. I don't expect you to care about it but that doesn't > mean you should prevent it from being in the release. I totally agree that > it needs to be fixed, but don't act like it is any different from the myriad > of other things that we release, some of which are broken as well. Besides > the main stuff that is broken w/ Maven is not the core pieces, but contribs. > this is still a serious problem to me, especially if we are going the path of modularizing lucene, then it will become even more serious in the future. i'm not trying to 'prevent' maven from being part of the release. I'm trying to get resolution on this maven issue, for which consensus does not exist. I get your reasoning, but unfortunately, because you don't understand how > Maven works you don't realize why maintaining it downstream is not an > option. Sorry. > i admit i dont understand how maven works, but it does seem to be a viable alternative. Just because you don't personally like that alternative, doesn't mean that its completely invalid. -- Robert Muir [email protected]
