I think I've fixed it now. I've upgraded the dependency to a later version of the woodstox library. It also breaks due to a broken sha1 checksum on its dependency stax2-api.jar. To get around that I've added stax2-api.jar to the "repo" directory within osmosis which is searched first.
Brett Henderson wrote: > This woodstox breakage is frustrating. The build broke a few weeks > back because I was auto selecting the latest version of the woodstox > libraries. The latest version introduced had broken checksums so I > locked it at the last working version. Now that also has broken > checksums. > > The fallback I have is to check a valid woodstox library into the > osmosis/repo directory which is searched before public repositories. > I don't have time to do it now unfortunately. > > If somebody has the time, download the woodstox 3.2.8 library and put > it into the osmosis/repo directory structure along with a matching ivy > config file. The existing libraries there can be used as an example. > > Relying on public repositories is always fraught with danger. Perhaps > I should look at configuring a repository on the osm dev server with > all required libs ... > > Brett Henderson wrote: >> All ivy files are stored in <homedir>/.ivy2 >> >> The Internet downloaded files are under the cache directory. The >> Woodstox Stax xml parser should be in there somewhere along with its >> sha1 value. Hopefully that is enough to get you by for now, I'll >> take a closer look as soon as I can. >> >> Frederik Ramm wrote: >>> Hi, >>> >>> I'm trying to build Osmosis trunk and I get an error from Ivy: >>> >>> [ivy:resolve] [FAILED ] >>> org.codehaus.woodstox#wstx-lgpl;3.2.8!wstx-lgpl.jar: invalid sha1: >>> expected=8898bbf8f5b17f5e59dde8324eceba6469171766 >>> computed=833a57ee3dc3aa7ac347c8dea98dc38de42e4938 (10409ms) >>> >>> Hacker that I am, I grepped through the files for the "expected" >>> value, hoping to be able to simply change it so that the above check >>> succeeds, but I could not find it. Can somebody tell me how this can >>> be fixed, or can I possibly build Osmosis without "wstx", whatever >>> that may be? >>> >>> Bye >>> Frederik >>> >>> >> >> > > _______________________________________________ osmosis-dev mailing list [email protected] http://lists.openstreetmap.org/listinfo/osmosis-dev
