> Before we can really vote I think we need to have a common approach to > this. One idea proposed by Andrew was Jakarta Common 'luceneappext' > (long word, how about just LuceneApps?) subproject. This would mean > org.apache.commons.luceneappext. > On the other had Andrew said that he thinks of scratchpad as only > another build target, so that implies keeping this under Lucene's > Jakarta project. > What you are suggesting is keeping it all within Lucene repository, > etc. > So which one is it? :)
> I think it may be easier to go with Jakarta Commons Sandbox, but I > think the purpose of that Sandbox is that when code matures it migrates > to Commons proper, and not elsewhere (not to Lucene). I could be > wrong, maybe there are examples/subprojects that can easily show that > I'm wrong :). In that case I'd vote for Jakarta Commons Sandbox > approach, as I feel that it will be more clear that this is > experimental/work-in-progress code. Generally the commons projects aren't "scratchpads" for extending the functionality for a particular project. Anyhow, that was more of an exasperated "not another, here or there catch-22 discussion" -- so anyhow. Anyhow, we don't need to vote on whether I can create a commons project for this. Probably what I envision happening is me going over there getting rejected because it should be here and here rejected bacause it should be there. So we're voting on "create scratchpad target for lucene in the lucene repository" -- if not then I'll go get rejected on Commons because it should be here. (Catch-22) -Andy -------------------------------------------------------------------- mail2web - Check your email from the web at http://mail2web.com/ . -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
