Fix/mvn settings cli

[guillermogutierrez]

[XXXX-<Title> - Please use the Work Item number and Title as PR Name, not subtasks]

📲 What

Autogenerates the maven settings.xml file

🤔 Why

The archetype:generate-from-project needs the settings.xml to be present in the local environment. As this is not a mandatory maven file, we need to ensure that a version exists, if not the build will fail.

🛠 How

Plugin (write-text-files-maven-plugin) capable to generate files has been added to the stacksclipom.xml file

<groupId>ru.yaal.maven</groupId>
<artifactId>write-text-files-maven-plugin</artifactId>
<version>1.1</version>

Also two new profiles were added (generate-settings-file and clean-workload)

• generate-settings-file. Is responsible for generate and store a temp settings file in ${output.basedir}/settings.xml
• clean-workload. Deletes the file once the entire CLI process is completed.

👀 Evidence

Screenshots / external resources / links / etc.
Link to documentation updated with changes impacted in the PR

🕵️ How to test

Notes for QA

✅ Acceptance criteria Checklist

• Code peer reviewed?
• Documentation has been updated to reflect the changes?
• Passing all automated tests, including a successful deployment?
• Passing any exploratory testing?
• Rebased/merged with latest changes from development and re-tested?
• Meeting the Coding Standards?

[guillermogutierrez]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information