Re: [Aperture-devel] Maven dependency on Aperture

[Christiaan F. <chr...@ad...>]

Jukka Zitting wrote:
> As discussed before, I'm looking at adding an Aperture binding to the
> Apache Tika project. Tika uses Maven 2 to handle builds and
> dependencies, so it would be very useful if the Aperture jars would be
> made available on the central Maven repository.

I'm very much in favor of both splitting up in various jars and making 
it available as Maven bundles.

The issue I frequently bump into myself is that I need to use the MIME 
type identifier and I do not have any need for the rest of Aperture.

How about the following split up:

aperture-api  (APIs and util classes used throughout the code)
aperture-extractors  (all extractors)
aperture-crawlers  (all crawlers, includes accessors as well?)
aperture-mime  (my precious MIME type identifier :) )

Of course a onejar jar file can still be provided as well.

A more extreme setup is to create separate jars for each extractor, 
crawler, etc, (i.e. for each implementation of an Aperture API) but that 
would probably only be practical for people that use Maven in their own 
apps.

BTW: making releases available through a Maven repository is one thing, 
using Maven to build the release is another thing. How do people feel 
about using Maven for Aperture's future development? Here at Aduna we 
have gathered quite some experience with Maven in the last year + we 
have an infrastructure (SVN, build server, Maven repositories for 
snapshots and releases, ...) that we can use.

> Also, due to the viral nature of the OSL, Tika can't depend on or
> bundle any of the Aperture implementation classes. What we can do is
> depend on the Aperture API interfaces, as their license is less
> restrictive. However, currently the main Aperture jar file mixes these
> classes together, which makes it difficult to distinguish between
> classes under different licenses. Would it be possible to create
> separate aperture-api and aperture-impl jars to make the distinction
> clearer?

Given what Leo has said on this topic, did this alter your opinion? Or 
perhaps your hands are tied due to Apaches policies? Though we took 
great care in choosing our licenses, we are always open to discuss and 
reconsider. If our licensing prohibits the use of our software for a 
substantial group of users, then clearly we have some work to do.


Kind regards,

Chris
--