Hi All, I've just changed how the PBF support is provided in Osmosis. Up until now there was a pre-compiled jar called osmpbf.jar checked into the Osmosis source tree. It was compiled from Scott Crosby's github project here: https://github.com/scrosby/OSM-binary
The problem with this is that it prevents me from publishing Osmosis to Maven Central because people trying to download Osmosis would be unable to use PBF without also getting a copy of that library. To get around this I've repackaged the OSM-binary project to build as part of the Osmosis source tree. The resultant jar is called osmosis-osm-binary, and it lives in a package called org.openstreetmap.osmosis.osmbinary. I've tried to do this in a way that allows me to keep up to date with the upstream project. I've forked the original repository on Github, and created an Osmosis branch: https://github.com/brettch/OSM-binary/tree/osmosis When changes are made to upstream, I should be able to merge master across to my osmosis branch. The resultant tree is then checked directly into the Osmosis source tree. On my local machine I actually have both git repositories acting on the same source files so it isn't too painful. I have the Osmosis source checked out normally (ie. a .git directory at the root), and the osmosis-osm-binary project is also a clone of my forked OSM-binary project (ie. I have a .git directory in there as well). So far it seems to work well enough. If the original OSM-binary project ever gets published to Maven Central directly then I can stop these shenanigans and depend on it directly. If anybody has any questions, issues, suggestions, etc let me know. Brett PS. I'm getting close to publishing to Maven Central now. There are no major blockers left that I'm aware of.
_______________________________________________ osmosis-dev mailing list [email protected] http://lists.openstreetmap.org/listinfo/osmosis-dev
