Consider making FileTailingEvent#getMessage() method public

[Toparvion]

Expected Behavior

FileTailingMessageProducerSupport.FileTailingEvent#getMessage method might be public instead of protected to allow application code be aware of what is happening with a file being tailed.

Current Behavior

Currently, when handling FileTailingEvents, application listeners have no access to the message produced by the underlying tail implementation. Therefore they cannot distinguish one file event type from another (e.g. absence from rotating) thus making the handling inefficient.

Context

I realize that it is generally not a good idea to rely on the text of the event as it comes from the underlying tailing provider (such as Apache Commons or OS Delegate) and thus can vary greatly depending on the platform. Nonetheless, there are some use cases where the message is still needed, for example:

• to handle the event appropriately if the tail implementation is fixed and is known beforehand
• to build some 'heuristic' around the message to cover different implementations where needed
• just to inform the end user (toString() method is too verbose for that)

The only alternative I see at the moment is to parse the toString() method output but it seems irrational and brittle.

If there is no security/compatibility/etc reason for keeping the method protected, I would submit a pull request making it public with the corresponding javadoc warning about its changeable nature.

[garyrussell]

I am sure this was just a simple mistake (probably some IDE auto-created getter); I can't believe it has taken 7 years for this to be reported.

[artembilan]

@Toparvion ,
please, consider to raise a simple PR!

Thanks

[Toparvion]

@artembilan , @garyrussell , thank you for the welcoming reply!
I've submitted the pull request.