search

tawfiqdawod / osmdroid

Automatically exported from code.google.com/p/osmdroid
0 stars 0 forks source link

osmdroid-third-party and Mapsforge new API #389

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
Hi,

The Mapsforge API was changed considerably at trunk version (with most changes 
at overlay API), not been anymore compatible with Google API add-on.
This cause the osmdroid-third-party not able to compile against the later 
Mapsforge trunk version code.

Thanks.

Original issue reported on code.google.com by devemu...@gmail.com on 20 Dec 2012 at 8:48

GoogleCodeExporter commented 8 years ago 
What do you suggest? Documenting the fact that it only works for 0.3.0?  As you 
say, it's unlikely to work with later versions because the osmdroid API is 
deliberately the same as Google and mapsforge is moving away from it.

Original comment by neilboyd on 20 Dec 2012 at 11:01

GoogleCodeExporter commented 8 years ago 
Well personally I use the osmdroid-third-party but not for its mapsforge 
wrapper. I have to remove the wrapper classes in order to compile it.
But eventually the osmdroid-third-party does not compile anymore with the 
latest mapsforge trunk version, if you want to still support it may be changes 
have to be made or drop its support?
Still it is a problem for those who use later version of mapsforge than 0.3.0

Original comment by devemu...@gmail.com on 20 Dec 2012 at 11:11

GoogleCodeExporter commented 8 years ago 
I haven't looked at the code for a long time, but actually there's an empty 
mapsforge jar in the downloads section that allows you to compile as-is.

But I guess you're right, if there's no will to upgrade then it should be 
removed.

Original comment by neilboyd on 20 Dec 2012 at 2:14

GoogleCodeExporter commented 8 years ago 
Actually the empty mapsforge jar conflicts with the regular full one if we want 
to have at a project's classpath both osmdroid and mapsforge full libraries.

Original comment by devemu...@gmail.com on 4 Apr 2013 at 6:07

GoogleCodeExporter commented 8 years ago 
If we've come to conclusion that the mapsforge wrapper stuff is obsolete, I'd 
like to remove it. Mapsforge is not in central repo and it is the last big 
hurdle in the build instructions on the Maven wiki page.

Original comment by kurtzm...@gmail.com on 13 Apr 2013 at 1:23

GoogleCodeExporter commented 8 years ago 
Seems like a fair conclusion

Original comment by neilboyd on 13 Apr 2013 at 6:40

GoogleCodeExporter commented 8 years ago 
This issue was closed by revision r1217.

Original comment by kurtzm...@gmail.com on 13 Apr 2013 at 8:06