Update Mavlink library

[arthurbenemann]

Updated the message_definitions files using current ArduPilot definitions.

Regenerated the message files using the pyMavlinkGenerator.

[arthurbenemann]

@ne0fhyk Care to take a look at this PR? We need the new camera_feedback and terrain_following type messages.

[m4gr3d]

@arthurbenemann I'm on it.
By the way, what's the source for the mavlink java generator script. A javadoc should be added to the generated file(s) to notify the user they were generated automatically, and they should not be updated.

[arthurbenemann]

The source for the generator is at :
https://github.com/DroidPlanner/droidplanner/blob/master/Mavlink/mavlinkGenerator/generateMessages.py

Some extra info at: https://github.com/DroidPlanner/droidplanner/blob/master/Mavlink/mavlinkGenerator/README.txt

The pymavlink code that we use is at:
https://github.com/DroidPlanner/mavlink

The correct way to do this would be to synchronize with the official MAVLink repo. Here is the PR mavlink/mavlink#246

[m4gr3d]

@arthurbenemann this PR looks good. Are you done working on it? It is ready for a merge?

[m4gr3d]

@arthurbenemann what issues is @LorenzMeier referring about for the mavlink/mavlink#246 PR.

Also, is there a reason why the generated classes name don't follow the java class name convention?

[arthurbenemann]

I'm merging this PR.

@ne0fhyk The issues are just so it's compatible with the mavlink project.

[m4gr3d]

@arthurbenemann is the class name convention also dictated by the mavlink project?
When I get some time, I might take a look at fixing up the mavlink project to incorporate the changes I mentioned, and sync it up with the official mavlink repo.

[arthurbenemann]

@ne0fhyk Not really, but they want the generator to be generic (not just for the ardupilotmega dialect).