Layout of how the plugin's YAML configuration file could look like.

[Luiz-Micci]

It is already established that we will use a YAML file as the plugin's configuration file.

We chose YAML because it is commonly used for pipeline automation...

Here's a proposed format:

mappings:
  - file: pom.xml
     placeholders:
       - query: /project/groupId
         name: Cookiecutter.param.groupId
  
  - file: ./config/file.properties
    placeholders:
        - query: parametro1
          name: valor1

From this format, we need to discuss how this file and its functionality will evolve.

[Luiz-Micci]

The interface that is going to read this config file could be the following structure:

• path- The path of the YAML file to be read.
• class- The Java class representing the structure of the YAML file.
• return object- A Java object corresponding to the read at the file.
• throws - IOException If an error occurs while reading the file. We could implement a Exception for the ConfigReader

[Luiz-Micci]

The classe object with the structure of the YAML file, could be like this:

Object Mapping having:

• Source file
• Target file
• A list with Translate Object

Object Translate with:

• key value
• target vaule

and a Object with a List of Mapping

[Luiz-Micci]

It is being done on issue #19

[BeppeTW]

#19