logo separator

[mkgmap-dev] [PATCH] Use Apache Ivy to fetch dependencies, put them in dist

From Richard Hansen rhansen at bbn.com on Sun Jan 22 23:55:57 GMT 2012

On 2012-01-22 16:25, Steve Ratcliffe wrote:
> Hi
>> Attached is a first attempt at tweaking the build system to
>> automatically fetch the pbf, junit, and macker dependencies as needed.
> I have created a branch 'build' and applied this patch to it.

Excellent, thank you.

> You will have to manually copy the osmpbf.jar file from splitter to
> build-support/repo/crosby/osmpbf/1.1.1-754a33af/jars/osmpbf.jar
> if you want to try it out.

I emailed Scott Crosby to ask if he'd be willing to publish osmpbf to 
the Maven Central Repository.  If it is published, ivy can download it 
and we can get rid of the build-support/repo directory entirely.

Until that happens, is the jar too big to check in to the mkgmap svn 
repository (~200KB)?  It's lgpl, so we'd have to make sure we have 
access to the source code in case anyone asks.

Alternatively, we can configure ivy to download the jar from osmosis's 
files at GitHub.  I skimmed GitHub's terms of service and didn't see 
anything prohibiting such usage, but we would probably want to ask 
permission anyway.

osmpbf has also been published at 
<http://repo.opengeo.org/crosby/binary/osmpbf/>, but I am unfamiliar 
with opengeo.org and their usage policies.  Also, the POM's sha1 and md5 
checksum files don't match the POM's contents so Ivy refuses to download 
it (unless we turn off checksum checks, which seems risky).

> I have a few comments, but I'm going to play with it a bit more first.
> There are also add-on files under the 'extra' directory which also
> need third party jar files, so I think this would be very useful for
> them.

We could perhaps add an 'extras' ant target that downloads those 
dependencies and builds those sources.  Or they could be moved into the 
main build.


More information about the mkgmap-dev mailing list