[GraphHopper] refactoring

[Peter K]

Hi,

@NopMap and I are working on improving a lot more stuff as you can see
in this github pulse summary:

https://github.com/graphhopper/graphhopper/pulse/monthly

To make it more comfortable for new Java developers I've moved the code
base to use setters and getters instead of the property-alike access
before. See here:
https://github.com/graphhopper/graphhopper/issues/81

Also the formatting is now changed to a more clear format where e.g.
brackets of one if-statement are aligned. NetBeans users don't need to
change anything as the properties should be automatically picked up from
the pom.xml.

If you have problems to upgrade your code to the new style feel free to
ask! (For IDE related stuff I fear I cannot be of a big help if it isn't
NetBeans but you can still try)

Last but not least I've moved the DataAccess interface to a byte-based
access where now Strings etc can be stored. This is one step towards
fixing issue #23. This change shouldn't affect your code (ie. the higher
level API) but there is still one bug for very large areas. Until this
will be fixed (soon!) you can work around this by avoiding
graphhopper.cleanUp

No major refactoring before releasing 0.1 is planed.

Regards,
Peter.