+1 indeed.
I am a long time Lucene user and as long as I remember I consumed Lucene
as maven artifact.
I even didn't knew that there is such a huge discussion around it within
the Lucene
dev community. I always took it as given that any bigger open source
project releases maven
artifacts ourdays.
As pointed out, maven is a de-facto standard at the moment. Not
publishing maven artifacts will cause an outcry amongst the end users.
It also means that someone outside the dev community will at some stage
create some
pom files and upload the artifact to a (semi-) public repository.
Is it not preferable to control what gets published? If there are errors
with the published artifacts
it will not affect the person who uploaded it, but everyone will blame the
Lucene devs.
--Hardy
On Tue, 18 Jan 2011 10:03:50 +0100, Simon Willnauer
<simon.willna...@googlemail.com> wrote:
On Tue, Jan 18, 2011 at 9:33 AM, Thomas Koch <tho...@koch.ro> wrote:
Hi,
the developers list may not be the right place to find strong maven
supporters. All developers know lucene from inside out and are
perfectly fine
to install lucene from whatever artifact.
Those people using maven are your end users, that propably don't even
subscribe to users@.
big +1 for this comment! I have to admit that I am not a big maven fan
and each time I have to use it its a pain in the ass but it is the
de-facto standard for the majority of java projects on this planet so
really there is not much of an option in my opinion. A project like
lucene has to release maven artifacts even if its a pain.
Simon
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
