[WIT-3064] Tech Adapter Framework autoconfiguration is not set up correctly

# Bug fixes

* Fixes a bug where autoconfiguration would not be scanned by Spring Boot following the recommended usage

# Related issue

Closes WIT-3064

# Definition of Done

So you are going to put your MR in review, but are you sure you have done all things listed here?

## All Developments

- [x] **Feature was implemented as per the requirements**
- [x] **If some code parts are complex they must be commented with code documentation**
- [x] **Unit, integration and E2E tests have been performed and code coverage is not reduced**, so that new code is covered
- [x] **CI/CD is successful**
- [x] **Exceptions and errors are handled, returning meaningful errors to the user**, without letting the underlying framework to respond with a generic Internal Server Error. Technical details are stored in the errors/problems and not in the user message
- [x] **Documentation (user documentation, HLD and others) has been updated**
  - Documentation has been updated with explanation of the new feature if it's user-facing (e.g. component now has additional setting) or it impacts them in some other way (e.g. optional field that becomes mandatory)
  - If it is a breaking change, we have documented it as such in the MR description in a "Breaking Changes" section
- [x] **Helm chart and other DevOps artifacts** have been updated and are valid deployment tools for the new version
- [x] **Problematic information (sensitive information, credentials, customer information or other intellectual property) is not included in the changes** as they could end up being public (most SPs are already published and automatically mirrored on every merge)
- [x] **Feature doesn't negatively affect any existing environments**, especially the clients Playgrounds. This means that merging it to master and deploying it to these environments will not break them and **no manual operations that are not reported in the documentation will be needed**
- [x] **If dependencies were changed, be sure that they will not impact the project**, that their license is compatible, and that they introduce no vulnerabilities
- [x] **Security, Authentication and Authorization have been considered**. No SQL injection, tokens handling, RBAC integration. Common security vulnerabilities identified and resolved
- [x] **The Java Scaffold is updated to support and test the new features**, especially if they're breaking changes

## API related Development

- [ ] **API Parameters and return body are compliant** with the API specification
- [ ] **Errors are correctly handled**, respecting the type of errors return bodies and responses for each endpoint
- [ ] **API is logging in compliance with audit standards**, presence of sensitive information for GDPR has been assessed and removed or managed in case is needed

## DB related Development

- [ ] **The database schema is designed to accurately** represent the data model and meet the requirements
- [ ] **Tables, relationships, and constraints (e.g. primary keys, foreign keys, unique constraints) are defined appropriately**, following best practices and a common naming convention
- [ ] **Sensitive data is stored securely**, encrypted if required, and access is restricted to authorized users
- [ ] **Migration scripts to upgrade and downgrade the database have been implemented and tested**

Author: Sergio Andres Mejia Tovar

RELEASE_NOTES.md

@@ -2,10 +2,46 @@
 
 All notable changes to this project will be documented in this file.
 
-## v2.2.0
+## v1.0.0-2.2.0
 
 ### Commits
 
+- **[WIT-3064] Tech Adapter Framework autoconfiguration is not set up correctly**
+  > 
+  > ##### Bug fixes
+  > 
+  > * Fixes a bug where autoconfiguration would not be scanned by Spring Boot following the recommended usage
+  >
+  > ##### Related issue
+  >
+  > Closes WIT-3064
+  >
+
+- **[WIT-2944] Publish java tech adapter framework to maven central**
+  > 
+  > ##### Bug fixes
+  > 
+  > Fixes on Central publish
+  > 
+  > ##### Related issue
+  > 
+  > Closes WIT-2944
+  > 
+  > 
+
+- **[WIT-2944] Publish java tech adapter framework to maven central**
+  > 
+  > ##### New features and improvements
+  > 
+  > * Added Maven profile to publish artifacts on Sonatype Central with all necessary plugins
+  > * Reintroduces the publish step on the CI
+  > 
+  > ##### Related issue
+  > 
+  > Closes WIT-2944
+  > 
+  >
+
 - **[WIT-2983] Add support for data contract and tags on java framework**
   > 
   > ##### New features and improvements
@@ -17,7 +53,7 @@ All notable changes to this project will be documented in this file.
   > 
   > Closes WIT-2983
   > 
-  > 
+  >
 
 - **[WIT-2829] Implement the sync java tech adapter framework**
   > 
@@ -70,5 +106,3 @@ All notable changes to this project will be documented in this file.
   > Closes WIT-2826
   > 
   > 
-
-- **Add README**

core/src/main/java/com/witboost/provisioning/framework/JavaTechAdapterFramework.java renamed to core/src/main/java/com/witboost/provisioning/JavaTechAdapterFramework.java

@@ -1,4 +1,4 @@
-package com.witboost.provisioning.framework;
+package com.witboost.provisioning;
 
 /**
  * Empty class to be used as a hook to enable package scanning by Spring Boot. It is intended to be part of the {@code @SpringBootApplication scanBasePackageClasses} and

core/src/main/java/com/witboost/provisioning/autoconfigure/ProvisionAutoConfiguration.java

@@ -22,14 +22,14 @@ public class ProvisionAutoConfiguration {
 
     @Bean
     @ConditionalOnMissingBean
-    public ProvisionConfiguration provisionConfiguration() {
+    public ProvisionConfiguration defaultProvisionConfiguration() {
         return new ProvisionConfiguration(
                 new ProvisionService() {}, new ProvisionService() {}, new ProvisionService() {});
     }
 
     @Bean
     @ConditionalOnMissingBean
-    ProvisionService provisionService() {
+    ProvisionService defaultProvisionService() {
         return new ProvisionService() {};
     }
 }

core/src/main/java/com/witboost/provisioning/autoconfigure/ValidationAutoConfiguration.java

@@ -28,7 +28,7 @@ public class ValidationAutoConfiguration {
 
     @Bean
     @ConditionalOnMissingBean
-    public ValidationConfiguration validationConfiguration() {
+    public ValidationConfiguration defaultValidationConfiguration() {
         return new ValidationConfiguration(
                 new ComponentValidationService() {},
                 new ComponentValidationService() {},
@@ -37,13 +37,13 @@ public ValidationConfiguration validationConfiguration() {
 
     @Bean
     @ConditionalOnMissingBean
-    public SpecificClassProvider specificMapper() {
+    public SpecificClassProvider defaultSpecificMapper() {
         return SpecificClassProviderImpl.builder().build();
     }
 
     @Bean
     @ConditionalOnMissingBean
-    public ComponentClassProvider componentClassProvider() {
+    public ComponentClassProvider defaultComponentClassProvider() {
         return ComponentClassProviderImpl.builder().build();
     }
 }

core/src/test/java/com/witboost/provisioning/framework/service/SyncTechAdapterServiceTest.java

@@ -39,7 +39,8 @@ public class SyncTechAdapterServiceTest {
     private ValidationService validationService;
 
     @Spy
-    private ProvisionConfiguration provisionConfiguration = new ProvisionAutoConfiguration().provisionConfiguration();
+    private ProvisionConfiguration provisionConfiguration =
+            new ProvisionAutoConfiguration().defaultProvisionConfiguration();
 
     @InjectMocks
     private SyncTechAdapterService techAdapterService;

core/src/test/java/com/witboost/provisioning/framework/service/validation/ValidationServiceTest.java

@@ -34,7 +34,8 @@ public class ValidationServiceTest {
     ComponentClassProvider componentClassProvider;
 
     @Spy
-    ValidationConfiguration validationConfiguration = new ValidationAutoConfiguration().validationConfiguration();
+    ValidationConfiguration validationConfiguration =
+            new ValidationAutoConfiguration().defaultValidationConfiguration();
 
     @Mock
     SpecificClassProvider specificClassProvider;

docs/usage.md

@@ -39,7 +39,7 @@ Where `X.X.X-Y.Y.Y` is the desired version of the framework. See [Publishing](..
 After including the dependencies, define you Main class as follows:
 
 ```java
-import com.witboost.provisioning.framework.JavaTechAdapterFramework;
+import com.witboost.provisioning.JavaTechAdapterFramework;
 
 @SpringBootApplication (scanBasePackageClasses = {JavaTechAdapterFramework.class, Main.class})
 @ConfigurationPropertiesScan(basePackageClasses = {JavaTechAdapterFramework.class, Main.class})
@@ -52,7 +52,7 @@ public class Main {
 }
 ```
 
-By adding `com.witboost.provisioning.framework.JavaTechAdapterFramework` on the Spring Boot annotations, you are instructing your application to scan the framework package as well for the service beans, regardless of your package definition.
+By adding `com.witboost.provisioning.JavaTechAdapterFramework` on the Spring Boot annotations, you are instructing your application to scan the framework package as well for the service beans, regardless of your package definition.
 
 With a single class, you now have a fully-functional Tech Adapter that receives and parses requests. At this point however, it will always return some kind of error, as it falls into its default configuration, so the next step is to implement your own business logic: