On 1/17/2011 at 11:25 AM, Robert Muir wrote: > On Mon, Jan 17, 2011 at 11:06 AM, Steven A Rowe <sar...@syr.edu> wrote: > > On 1/17/2011 at 1:53 AM, Michael Busch wrote: > >> I don't think any user needs the ability to run an ant target on > >> Lucene's sources to produce maven artifacts > > > > I want to be able to make modifications to the Lucene source, install > > Maven snapshot artifacts in my local repository, then depend on those > > snapshots from other projects. I doubt I'm alone. > > And personally I would be totally fine with this, where maven is in > /dev-tools, just like eclipse and idea configuration, and we can even > put a whole README.txt in there that says "these are tools for > developers and if they start rotting they will be deleted without a > second thought". > > but requiring special artifacts is a different story
I have it wrong in LUCENE-2657. It creates "special" artifacts intended for publishing via public Maven repositories. But for the purposes of publishing (as opposed to locally modified sources), the artifacts published through public Maven repositories should be *exactly* the same ones produced by the Ant build, with the obvious exception of the POMs. This is the model used by previous releases, and if we continue the tradition of publishing Maven artifacts (as we have since the 1.9.1 release), the model should not change. Steve
