Renaming handlers for other kinds of declarations

[pauloborba]

Field declarations would only be relevant in case of multiple lines field declarations, otherwise unstructured and semistructured merge report the same conflicts (we have talked about this long time ago). Entire files are handled reporting the same result of unstructured merge, also discussed long time ago. Finally, innerclasses are handled by other handler (DeletionsHandler).

we should empirically confirm that. enums might be a target.

[guilhermejccavalcanti]

Let's enumerate the possible cases, and how it works currently:

• field declarations: there is no treatment based on the hypothesis that this would only be relevant in case of multiple lines field declarations. Lacks empirical validation.

• enums methods and constructors: are handled as classes, i.e, internaly there is no difference between enum methods and class methods

• entire files: are handled by unstructured merge

• inner classes and enums: are handled in a separate handler (https://github.com/guilhermejccavalcanti/jFSTMerge/blob/master/src/main/java/br/ufpe/cin/mergers/handlers/DeletionsHandler.java deserves a better name)

[pauloborba]

@jvcoutinho we should integrate alice's version (initialization handler), and discuss what to do with the other kinds of declarations

[jvcoutinho]

Will she create a pull request?

[pauloborba]

@jvcoutinho check if alice's version is specific to static block