Responding to the thread as a whole, having read it with great interest.
I'd be interested to know what packagers for distributions such as
debian and fedora do with systems that patch 3rd party dependencies.
I'll guess that if it is internalized as mentioned below that there is
no problem.
But I have no idea what would be the case if one were to say that
such-and-so part of Lucene did not work with a 3rd party external
dependency (say icu) unless it were patched in a particular way.
BTW, fedora 16 has lucene 2.9.4 and does not have solr. Looks like F17
will have the same. I'd also be interested to know why they don't have
3.x or solr.
-- DM
On 04/24/2012 10:02 AM, Robert Muir wrote:
On Tue, Apr 24, 2012 at 9:57 AM, Benson Margulies<[email protected]> wrote:
Maven is guilty as charged that the simple, obvious, way of dealing
with this requires publication. In the pressurized circumstances of
3.6.0, no one was going to get past that. Now, we can if you want.
well FWIW: we got past it for 3.6.0 by importing their source code and
renaming the packages to o.a.s.internal.xxxxx
Thats basically my question about this bugfix scenario, is this our
only real option for maven (suck in all the source code and repackage
it)?
I would like to have other options!
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
