[GraphHopper] Project structure

[evilhack at gmx.de]

Hi Peter,

 

I see, you changed your project structure by giving each subproject an own pom.xml. Is there any reason why you didn’t setup a Maven multi-module project since you now have several sub projects and one root project? 

I’m working with eclipse m2e and EGit and due the current single project structure I first have to to import the root project without maven nature to have a connection to the git-repository and afterwards I need to import all single projects (graphhopper-core etc.) to get maven integration; but there I don’t have a Git-connection anymore. This is kind of unhandy and has several drawbacks in my workflow (i.e. whenever my working copy differs from the Git-repository I need to synchronize the root project to get the changes into the sub projects, where I have file structure only).

I think a multi-module project (an additional pom.xml in the root project, with the submodules defined in) would solve those Problems. I’m not that familiar with setting up maven projects correctly, maybe you can think about doing this?


Best regards,

Karl.


PS: Any idea when you’re going to include turn costs/restrictions? Maybe I can help you with that somehow?
-------------- n�chster Teil --------------
Ein Dateianhang mit HTML-Daten wurde abgetrennt...
URL: <http://lists.openstreetmap.org/pipermail/graphhopper/attachments/20130430/8deca5d6/attachment.html>