Refactoring directory structure

[maheshkelkar]

Currently all the files/modules are located in top package level agent directory.

@cyrille-leclerc let me know if you are ok if I restructure the modules into separate directories? It will really help with manageability.

E.g.
com.jmxtrans.agent

• util - contains utility (as-is)
• outputWriter - contains abstract & derived writers
• resultNameStrategy - contains result name transform code (as-is)
• agent, agent builder, query, invocations, etc. code resides in the top level dir

[kerlandsson]

Cleaning up the directory structure would be appreciated. However, since several classes are referenced by qualified name in the configuration (e.g. output writers) file we cannot move them without breaking backwards compatibility.

[gliptak]

What would be a good approach to backwards compatibility for a refactoring like this? When do you see deprecated being removed?

[kerlandsson]

@gliptak In my opinion, the benefits of cleaning up the directory structure are not big enough to warrant breaking existing configurations. I would suggest an approach where we try to move things that are not referenced in the configuration file and let the rest be.

[cyrille-leclerc]

+1 on @kerlandsson's proposal