Re: apache-solr packaging?

On Wed, Oct 26, 2011 at 2:06 AM, David Walluck <[email protected]> wrote:
> On 10/26/2011 01:40 AM, Nico Kadel-Garcia wrote:
>>
>> I took the apache-solr package from Fedora 14, which works and is
>> cleanly buildable and installable on Fedora 14 and 15. I then tried to
>> compile it under RHEL 5, both with and without JPackage 6.0. Hilarity
>> ensued, especially as I tried to build the toolchain for
>> lucene-contrib and the toolchain to build *THAT*.
>
> I didn't use the Fedora RPM, but all I had to do was upgrade lucene 2.x in
> JPackage 6 first.
>
> Don't get me wrong---it was a lot of work to upgrade from the 1.3.x version
> because of the additional dependencies.

Yeah, that "hilarity ensued" comment of mine has happened before.

>> I'm delighted you've already published an SRPM for apache-solr-1.3 in
>> JPackage 6.0, and look forward to testing the SRPM for 1.4.1. The new
>
> I built 1.4.1 on the JPackage build system. There's some problem with my
> setup and I can't push it at the moment.
>
> There's also a part in the build where I see that it is downloading three
> jars from the net. I assume that Fedora is not building any of the contrib
> stuff. I build everything, but I bundle a couple jars that we don't have:
> carrot2-mini jar and commons-csv.

Indeed. That part ticked me off, because most of those hard-coded
URL's are *broken" with an upstream re-arrangement of the Maven
repositories. It's as bad as a Perl module reaching ot CPAN in the
build process, and it's not the first time I've encountered it with
software that is assembled from a suite of other components.

> I can't even find the source code for the commons-csv jar, but it apparently
> builds against the standard Apache version, so I am not even sure if that's
> needed right now.

Hard for me to tell: I'm much more of a packager than a Java author,
and can't tell what features might wind up disabled by the lack.