: - I'm definitely for separate source and binary releases - makes so : much more sense post merge. : solr's "src" is particularly great now... one can modify any part : (lucene, modules, etc) and easily rebuild.
agreed .. i'm just wondering if we really need both lucene-src and solr-src artifacts. particularly considering that solr-src is already a superset of lucene-src ... it just seems like one uber lucene-solr-src package of the "dev" tree would be the simplest most straight forward thing to ship for people who want source. (particularly looking forward to 4.0 when we'll also have "modules" in the top level ... should that really be a seperate src package?) The only advantage i can think of to having seperate solr/lucene src packages is the size issue ... the lucene-src by itself is much smaller and that has it's perks for people who really only want src ... but i still wonder about dev-tools (and modules) and wether it would make sense for the lucene-src package to be from the root of the "dev" tree but excluding ./solr? -Hoss --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
