[osmosis-dev] Setting Up an Eclipse Build-Environment

[Brett Henderson]

If you run "ant publish" from the root of the overall project it will copy
all required jars into each project.  I haven't tried to make Eclipse Ivy
aware.  "ant all" which achieve the same result but requires that you have
the apidb and pgsql test databases in place.

If you want to run Osmosis, the simplest way is to run "ant publish" from
the root, then run the package/bin/osmosis launcher as per normal.  There is
a fully working Osmosis within the package directory.

To run within Eclipse or use the debugger, I always use junit tests.  Within
each project, each test directory contains its own osmosis-plugins.conf that
loads only the plugins available within that project and its dependencies.
For example, the pgsnapshot project (the pgsql tasks) loads XML, dataset,
and pgsnapshot plugins.  Because each project already has all required
libraries on the classpath, you don't need to worry about the bootstrapping
via the classwords loader, or configuring plexus.conf.

If you develop a new plugin that is included in the main package, you will
always have to modify the package/config/osmosis-plugins.conf to load it.
You will also need to modify the ivy.xml in the package project to include
the plugin jar in the project.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/osmosis-dev/attachments/20100822/3ad580c8/attachment.html>