[osmosis-dev] Maven artifacts, using Osmosis as a library, OSMembrane
brett at bretth.com
Mon Nov 28 01:49:29 GMT 2011
On 27 November 2011 13:09, Andrew Byrd <andrew at fastmail.net> wrote:
> Hi Brett, Igor, and the rest of the list,
> Rather than reinvent the wheel I am considering using an Osmosis pipeline
> for bounding polygon and tag filtering as well as PBF support in the Open
> Trip Planner project. To do so we would need to add a Maven dependency on
> (parts of) Osmosis. I see that there is a Maven POM in the core Osmosis
> module, and a repository at
> http://oss.sonatype.org/**content/repositories/**openstreetmap-snapshots<http://oss.sonatype.org/content/repositories/openstreetmap-snapshots>but it contains only version 0.32.1-SNAPSHOT. I find only the Osmosis-core,
> without the other subprojects. Are artifacts still published somewhere?
I didn't know that existed! I suspect Hakan did it a while back. He
created the POM file that currently exists in the Osmosis distribution.
Unfortunately I broke the Maven build horribly when I split Osmosis into
multiple sub-projects in version 0.36.
I've been investigating publishing the Osmosis artefacts via Maven but it's
probably a long way off. I've re-factored the project structures to follow
a more maven-like layout, and I've re-factored tests to eliminate
dependencies on Ant-based test data preparation. Those changes are already
in the main github repo.
I've also started experimenting with a Maven based build, but it's early
days and I don't know how far I'll get.
> I see that there has also been some discussion on the list about using
> Osmosis as a library (quoted message below). Igor, based on a quick look at
> PipelineExecutor in the head revision of OSMembrane, it looks like you are
> calling Osmosis as an external program. Are you still planning to tighten
> the integration with Osmosis? What has been your experience using Osmosis
> in this way?
In theory it shouldn't be difficult to use Osmosis as a library. All tasks
can be invoked in isolation without using the entire command-line driven
pipeline. The projects could probably be structured more effectively, but
worst case you'll end up with some larger binaries.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the osmosis-dev