I don't think we really care if the tools remain in Lucene - that will allow some guy that cares about Maven to still make it all happen.
I think we are more saying, lets drop it from part of the official release process. When we release, we don't worry about Maven as part of the release process. We can leave the Maven support tools we have - but it will be up to someone to step up and handle the Maven part outside of the official release process. So we drop it from the release todo's and what not (moving it to another page about how to create the maven artifacts). Then those that release and don't want to deal with Maven do not have to. It won't fall on the RM to think about Maven by default. Mavens supporters will have to step in. - Mark On 9/18/10 12:02 PM, Ryan McKinley wrote: > I don't get what is being proposed... are you guys really suggesting > we drop the ant generate-maven-artifacts target? and let people who > use maven sort it out for themselves? Making sure the generated poms > are valid is another question > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
