On 1/17/2011 at 3:05 PM, Michael Busch wrote: > On 1/17/11 8:06 AM, Steven A Rowe 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. > > > > This is something I would feel comfortable not supporting in Lucene > out-of-the-box, because if someone needs to use modified sources it's > not unreasonable to expect that they can also create their own pom files > for the modified jars.
This makes zero sense to me - no one will ever make their own POMs, except maybe the empty shells Maven will auto-create for you when run the install:install-file goal. The key thing that LUCENE-2657 provides is POMs that can be verified correct via Maven itself - when Maven performs a build, the POMs are checked for correctness, and if the build fails, you can tell something is wrong. Anything short of that won't cut it long term. Maybe from your perspective building the project with the POMs is unnecessary, but from mine it is a *requirement*. And, happily IMHO, users get local build/install for free. Steve
