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

Tue Jan 31 00:13:04 GMT 2012

Hi

> Now that you've had a bit of time to play with the build system changes,
> what are your thoughts?  Do you feel comfortable merging the build
> branch to trunk?

I think that this will be really good, and I've been playing around
with it quite a lot over the last day or so.

There are a few more jars needed to set up a development environment
so that everything can be compiled. I added the following dependancies
to my working copy:

For the mkgmap ant task:
	<dependency org="org.apache.ant" name="ant" rev="1.8.2"
							conf="compile->compile(*)"/>

Development only (internationalisation):
	<dependency org="com.ibm.icu" name="icu4j" rev="4.8"
							conf="compile->compile(*)"/>

There is the optional DEM reader which needs the java JAI libraries. I
had trouble finding a good repository for this. The best I found is:

	<dependency org="javax.media.jai" 
name="com.springsource.javax.media.jai.codec" rev="1.1.3" 
conf="*->compile" />

   with the repository definition:

	<url name="com.springsource.repository.bundles.external">
		<ivy 
pattern="http://repository.springsource.com/ivy/bundles/external/[organisation]/[module]/[revision]/[artifact]-[revision].[ext]" 
/>
		<artifact 
pattern="http://repository.springsource.com/ivy/bundles/external/[organisation]/[module]/[revision]/[artifact]-[revision].[ext]" 
/>
	</url>

I think we should have three configurations, default/master for the normal
build, "optional" for things that are not part of the main
distribution but which people might like to use (including anything
where we cannot distribute the jars, which may be the case with JAI -
need more investigation) and "dev" to cover macker, icu4j etc.
The idea being that resolving dev would bring in everything needed to
get going.

I'd also like to remove the build-support directory, and just move the
scripts to the top level and combine them into one or even add them to
the build.xml. The ivy jar file can go under lib/build or something.

> Also, would you like me to work on modifying splitter's build system to
> match?

Yes that would be great.

Thanks
Steve