[OSM-dev] I've committed a whole new set of mappaint icons - how do I compile the jar file?!?

Ulf Lamping ulf.lamping at web.de
Sun Jul 15 00:42:18 BST 2007


Christof Dallermassl schrieb:
>> I would like to build a new mappaint.jar file (to include it into svn 
>> and also for some other experiments), but unfortunately my JAVA 
>> knowledge is a bit rusted (it's almost 10 years ago), and especially 
>> the build environment has completely changed since then.
>>
>> The only information I could find (at 
>> http://josm.eigenheimstrasse.de/wiki/DevelopingPlugins) is describing 
>> a bit of the internas, but not how to set up a plugin build environment.
>>
>> So what do I need? I guess: JAVA SDK and probably Eclipse? What do I 
>> have to start with?
>
> not that I know of. But it's quite simple: you need a java sdk 
> (version 1.5 or better). Eclipse is optional, but recommended (or any 
> other IDE).
>
> Subversion on command line or in eclipse to checkout the code (eclipse 
> needs a plugin to support subversion: I use subclipse (add update site 
> http://subclipse.tigris.org/update_1.2.x to eclipse (Menu 
> Help/Software Updates).
>
> ant (http://ant.apache.org) is the "make for java". It reads the 
> build.xml file and compiles, zips, etc. Download ant and install 
> somewhere. Add the bin directory to your path.
> "ant build" creates the new jar file.
>
> Optionally, ant can also be executed from within eclipse (and is also 
> included in eclipse). Just open the build.xml file and in the outline 
> view you can run ant for a given target.
>
> "ant install" copies the jar file into .josm/plugins.
>
First of all, thanks a lot, that was exactly what I needed :-)))

After tweaking with the paths (setting JAVA_HOME to the SDK bin dir and 
adding ant to the PATH) all is running smooth now. As my first steps 
with eclipse failed, I'm running ant from the command line, and 
compiling mappaint works smoothly now. As you might have seen, I'm 
already working on it, I've committed my first bugfix and I'm working 
now on more flexibility for the elemstyles.xml file (different rules for 
different zoom levels, rules for subkeys, ...) - it's currently just too 
simple for some interesting things ;-)

Regards, ULFL




More information about the dev mailing list