Hi Andrew, On 8 December 2011 00:18, Andrew Byrd <[email protected]> wrote:
> Brett and Igor, > > Thanks for your replies last week about using Osmosis as a library and a > Maven dependency. I hadn't spotted the Maven branch on the Github > repository so I appreciate you pointing that out, and I will be looking to > the tests for usage hints as you suggested, Igor. > The maven branch is woefully incomplete, but it's a start :-) It's not building at the moment, I seem to have some dependency mismatches between the Ivy and Maven configs. Probably not hard to fix. I've just merged in the latest 0.40.1 release which should be a good place to start. > With your comments in mind, some Open Trip Planner developers have > discussed this option and we would prefer to eventually add a dependency on > Osmosis rather than duplicate functionality. For the moment we will just be > using Osmosis as an external tool in scripts, but we would be happy to > contribute to the Mavenization effort and may even be able to offer space > on a Maven repository to host the artifacts. Just let me know if we can be > of assistance. > I'm not sure when I'll get back to the maven work, but I'd like to keep it going if I can. It's been more of an experiment than anything else. I'd like to eventually have the artefacts made available on a public maven repo one way or another. Whether it's easier to build the project via maven or bolt on maven repo publishing to the existing ant/ivy project I have no idea. Any help is appreciated :-) Brett
_______________________________________________ osmosis-dev mailing list [email protected] http://lists.openstreetmap.org/listinfo/osmosis-dev
