Improve Spark and Provenance modules

Author: FranckCo

.github/workflows/ci.yml

@@ -3,17 +3,54 @@ name: Trevas CI
 on:
   push:
   pull_request:
-    types: [opened, synchronize, reopened]
+    types: [ opened, synchronize, reopened ]
 
 jobs:
+  format:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+
+      - name: Set up JDK 17
+        uses: actions/setup-java@v4
+        with:
+          distribution: "temurin"
+          java-version: 17
+
+      - name: Cache Maven dependencies
+        uses: actions/cache@v4
+        with:
+          path: ~/.m2/repository
+          key: ${{ runner.os }}-maven-${{ hashFiles('**/pom.xml') }}
+          restore-keys: |
+            ${{ runner.os }}-maven-
+      - name: Verify code format with Spotless
+        run: mvn spotless:check
+  test-excluding-vtl-sdmx:
+    name: Run Trevas tests excluding vtl-sdmx module
+    runs-on: ubuntu-latest
+    needs: format
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+      - name: Set up Maven Central Repository
+        uses: actions/setup-java@v4
+        with:
+          java-version: 17
+          distribution: "adopt"
+      - name: Test
+        run: mvn test -pl '!vtl-sdmx'
   test:
     name: Run Trevas tests
     if: (github.repository != 'InseeFr/Trevas' &&
-        github.event_name == 'push') ||
-        (github.event.pull_request.head.repo.fork == true ||
-        (github.event.pull_request.head.repo.fork == false &&
-        github.event.pull_request.merged == false))
+      github.event_name == 'push') ||
+      (github.event.pull_request.head.repo.fork == true ||
+      (github.event.pull_request.head.repo.fork == false &&
+      github.event.pull_request.merged == false))
     runs-on: ubuntu-latest
+    needs: format
     steps:
       - uses: actions/checkout@v4
         with:
@@ -62,12 +99,13 @@ jobs:
   test-sonar-package:
     name: Run Trevas tests with coverage & sonar checks
     # Trevas main repo commit branch or merged PR
-    if: github.repository == 'InseeFr/Trevas' && 
-        (github.event_name == 'push' ||
-        github.event.pull_request.head.repo.fork == false ||
-        (github.event.pull_request.head.repo.fork == true &&
-        github.event.pull_request.merged == true))
+    if: github.repository == 'InseeFr/Trevas' &&
+      (github.event_name == 'push' ||
+      github.event.pull_request.head.repo.fork == false ||
+      (github.event.pull_request.head.repo.fork == true &&
+      github.event.pull_request.merged == true))
     runs-on: ubuntu-latest
+    needs: format
     steps:
       - uses: actions/checkout@v4
         with:

CONTRIBUTING.md

@@ -1,36 +1,45 @@
 # 🚀 Contributing to Trevas
 
-Thank you for your interest in contributing to Trevas! Your help is invaluable in improving this project. Here’s how you can get started.
+Thank you for your interest in contributing to Trevas! Your help is invaluable in improving this project. Here’s how you
+can get started.
 
 ## 🛠️ Contribution Guidelines
 
 ### 📌 Roles & Responsibilities
 
-- **[Insee](https://www.insee.fr/en)** is responsible for the overall **project governance**. They guide the vision of the project, make final decisions, and ensure the project aligns with its long-term goals.
-- **[Making Sense](https://making-sense.info/)** are responsible for reviewing **Pull Requests (PRs)**, merging them into the master branch, adjusting the **GitHub project board**, and tagging issues to ensure proper tracking. They ensure the code meets the project's standards before merging and help prioritize tasks.
-- **Maintainers** (which can include anyone who is granted this role) help with day-to-day management of the project, such as reviewing code, merging PRs, and managing the project's direction. If you're interested in becoming a maintainer, please see the section below.
+- **[Insee](https://www.insee.fr/en)** is responsible for the overall **project governance**. They guide the vision of
+  the project, make final decisions, and ensure the project aligns with its long-term goals.
+- **[Making Sense](https://making-sense.info/)** are responsible for reviewing **Pull Requests (PRs)**, merging them
+  into the master branch, adjusting the **GitHub project board**, and tagging issues to ensure proper tracking. They
+  ensure the code meets the project's standards before merging and help prioritize tasks.
+- **Maintainers** (which can include anyone who is granted this role) help with day-to-day management of the project,
+  such as reviewing code, merging PRs, and managing the project's direction. If you're interested in becoming a
+  maintainer, please see the section below.
 
 ### 📌 Issues & Pull Requests
 
 - Every **Pull Request (PR) must be linked to an existing issue**
 - When creating a PR, use the following naming convention:
-  - **`feat/your-feature-name`** for new features
-  - **`fix/your-bug-fix`** for bug fixes
+    - **`feat/your-feature-name`** for new features
+    - **`fix/your-bug-fix`** for bug fixes
 - Discuss your ideas in an issue before starting major work
 
 ### 👀 Four Eyes Principle & Code Review Practices
 
-To ensure the quality, reliability, and security of Trevas, we follow the **Four Eyes Principle** for all code contributions.
+To ensure the quality, reliability, and security of Trevas, we follow the **Four Eyes Principle** for all code
+contributions.
 
 #### 🔍 What is the Four Eyes Principle?
 
-The **Four Eyes Principle** means that **at least two people must review and approve any important action** before it is finalized. In the context of Trevas, this applies specifically to:
+The **Four Eyes Principle** means that **at least two people must review and approve any important action** before it is
+finalized. In the context of Trevas, this applies specifically to:
 
 - Pull Request (PR) reviews and approvals
 - Merges into the `develop` or `master` branches
 - Structural changes in architecture, testing strategy, or documentation
 
 This principle helps:
+
 - Catch potential bugs or security issues early
 - Encourage collaborative development
 - Share knowledge across the team
@@ -49,10 +58,12 @@ All Pull Requests should:
 
 **Only after meeting these conditions can a PR be merged**.
 
-Maintainers are expected to **uphold these principles** and ensure reviews are thoughtful, constructive, and inclusive.  
+Maintainers are expected to **uphold these principles** and ensure reviews are thoughtful, constructive, and
+inclusive.  
 We believe that code review is not just a checkpoint, but a space to learn, improve, and grow as a team.
 
-> 🤝 If you're contributing regularly and want to become a maintainer, don't hesitate to reach out to us at **contact@making-sense.info** — we’d love to welcome more eyes to the team!
+> 🤝 If you're contributing regularly and want to become a maintainer, don't hesitate to reach out to us at *
+*contact@making-sense.info** — we’d love to welcome more eyes to the team!
 
 ### 🧪 Test-Driven Development (TDD)
 
@@ -62,20 +73,82 @@ We encourage a **test-driven approach** to ensure code reliability and maintaina
 2. **Implement the code** needed to pass the test
 3. **Refactor** while ensuring all tests remain green
 
-### 🎨 Code Formatting
+### 🎨 Code Formatting with Spotless
+
+We use [Spotless](https://github.com/diffplug/spotless) to enforce consistent code formatting based on the *
+*[Google Java Style Guide](https://google.github.io/styleguide/javaguide.html)**.
+
+#### 💻 Check formatting
+
+Before committing, run:
+
+```bash
+mvn spotless:check
+```
+
+#### 🛠️ Auto-format your code
+
+To automatically format your code, run:
+
+```bash
+mvn spotless:apply
+```
+
+This ensures that your code:
+
+- Uses **tabs** for indentation
+- Respects a **120-character line limit**
+- Applies **Google Java Format**
+
+All contributions **must pass `spotless:check` in CI**.
+
+### 🧠 IntelliJ IDEA Setup for Spotless
+
+To use Spotless formatting from IntelliJ:
+
+1. **Enable necessary VM options** (required to support Google Java Format):
+
+   Go to:
+
+   ```
+   Preferences (macOS) or Settings (Windows/Linux) >
+   Build, Execution, Deployment >
+   Compiler >
+   Java Compiler >
+   Additional command line parameters
+   ```
+
+   Add the following VM options:
+
+   ```
+   --add-exports=jdk.compiler/com.sun.tools.javac.api=ALL-UNNAMED
+   --add-exports=jdk.compiler/com.sun.tools.javac.code=ALL-UNNAMED
+   --add-exports=jdk.compiler/com.sun.tools.javac.file=ALL-UNNAMED
+   --add-exports=jdk.compiler/com.sun.tools.javac.parser=ALL-UNNAMED
+   --add-exports=jdk.compiler/com.sun.tools.javac.tree=ALL-UNNAMED
+   --add-exports=jdk.compiler/com.sun.tools.javac.util=ALL-UNNAMED
+   ```
+
+2. **(Optional)**: Automate formatting on save using the *Save Actions* plugin:
+
+- Install the **Save Actions** plugin from the IntelliJ Marketplace
+- Go to `Preferences > Save Actions`
+- Enable **"Activate save actions on save"**
+- Configure it to run an external tool with the command:
 
-To keep our codebase consistent, please follow these formatting guidelines:
+  ```bash
+  mvn spotless:apply
+  ```
 
-- **Indentation**: Use tabs for indentation
-- **Line Length**: Keep lines under 120 characters
-- **Naming**: Use meaningful and descriptive English names for variables, functions, and classes
+> 💡 You can also define a custom keybinding in IntelliJ to run `mvn spotless:apply` easily when needed.
 
 ## 🔄 Creating a Pull Request
 
 To contribute, follow these steps:
 
 1. **Fork** the repository
-2. **Create a branch** from `develop` using the correct prefix (`feat/` or `fix/`). Example: `feat/authentication` or `fix/typo-readme`
+2. **Create a branch** from `develop` using the correct prefix (`feat/` or `fix/`). Example: `feat/authentication` or
+   `fix/typo-readme`
 3. **Commit** your changes with a clear and concise message
 4. **Push** your branch to your fork
 5. **Open a Pull Request** targeting the `develop` branch
@@ -100,7 +173,8 @@ Check out our [Project Board](https://github.com/InseeFr/Trevas/projects) to see
 ### 🗣️ Communication
 
 We encourage **open and transparent discussions**.  
-If you have any questions or suggestions, please use [GitHub Issues](https://github.com/InseeFr/Trevas/issues) so the whole community can participate.
+If you have any questions or suggestions, please use [GitHub Issues](https://github.com/InseeFr/Trevas/issues) so the
+whole community can participate.
 
 ## 📄 License
 

README.md

@@ -6,23 +6,32 @@ Transformation engine and validator for statistics.
 [![Quality Gate Status](https://sonarcloud.io/api/project_badges/measure?project=InseeFr_Trevas&metric=alert_status)](https://sonarcloud.io/dashboard?id=InseeFr_Trevas)
 [![Coverage](https://sonarcloud.io/api/project_badges/measure?project=InseeFr_Trevas&metric=coverage)](https://sonarcloud.io/dashboard?id=InseeFr_Trevas)
 [![Maven Central](https://maven-badges.herokuapp.com/maven-central/fr.insee.trevas/trevas-parent/badge.svg)](https://maven-badges.herokuapp.com/maven-central/fr.insee.trevas/trevas-parent)
+[![Javadoc](https://img.shields.io/badge/Javadoc-fr.insee.trevas-ff69b4?logo=java&style=flat-square)](https://javadoc.io/doc/fr.insee.trevas)
 [![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](https://opensource.org/licenses/MIT)
 [![Mentioned in Awesome Official Statistics ](https://awesome.re/mentioned-badge.svg)](http://www.awesomeofficialstatistics.org)
 
-Trevas is a Java engine for the Validation and Transformation Language (VTL), an [SDMX standard](https://sdmx.org/?page_id=5096) that allows the formal definition of algorithms to validate statistical data and calculate derived data. VTL is user oriented and provides a technology-neutral and standard view of statistical processes at the business level. Trevas supports the latest VTL version (v2.1, July 2024).
+Trevas is a Java engine for the Validation and Transformation Language (VTL),
+an [SDMX standard](https://sdmx.org/?page_id=5096) that allows the formal definition of algorithms to validate
+statistical data and calculate derived data. VTL is user oriented and provides a technology-neutral and standard view of
+statistical processes at the business level. Trevas supports the latest VTL version (v2.1, July 2024).
 
-For actual execution, VTL expressions need to be translated to the target runtime environment. Trevas provides this step for the Java platform, by using the VTL formal grammar and the [Antlr](https://www.antlr.org/) tool. For a given execution, Trevas receives the VTL expression and the data bindings that associate variable names in the expression to actual data sets. The execution results can then be retrieved from the bindings for further treatments.
+For actual execution, VTL expressions need to be translated to the target runtime environment. Trevas provides this step
+for the Java platform, by using the VTL formal grammar and the [Antlr](https://www.antlr.org/) tool. For a given
+execution, Trevas receives the VTL expression and the data bindings that associate variable names in the expression to
+actual data sets. The execution results can then be retrieved from the bindings for further treatments.
 
 Trevas provides an abstract definition of a Java VTL engine, as well as two concrete implementations:
 
-- an in-memory engine for relatively small data, for example at design time when developing and testing VTL expressions on data samples
+- an in-memory engine for relatively small data, for example at design time when developing and testing VTL expressions
+  on data samples
 - an [Apache Spark](https://spark.apache.org/) engine for Big Data production environments
 
 Other implementations can be easily developed for different contexts.
 
 ## Documentation
 
-The documentation can be found in the [docs](https://github.com/InseeFr/Trevas/tree/master/docs) folder and [browsed online](https://inseefr.github.io/Trevas).
+The documentation can be found in the [docs](https://github.com/InseeFr/Trevas/tree/master/docs) folder
+and [browsed online](https://inseefr.github.io/Trevas).
 
 If you want to contribute, see this [guide](docs/CONTRIBUTING.md).
 
@@ -48,4 +57,5 @@ Trevas is part of the [sdmx.io](https://www.sdmx.io/) ecosystem.
     <img  src="https://awesome.re/mentioned-badge.svg" />
 </p>
 
-Trevas is referenced by [_Awesome official statistics software_](https://github.com/SNStatComp/awesome-official-statistics-software).
+Trevas is referenced by [_Awesome official statistics
+software_](https://github.com/SNStatComp/awesome-official-statistics-software).

coverage/pom.xml

@@ -6,7 +6,7 @@
     <parent>
         <groupId>fr.insee.trevas</groupId>
         <artifactId>trevas-parent</artifactId>
-        <version>1.9.0</version>
+        <version>1.10.0</version>
     </parent>
 
     <artifactId>coverage</artifactId>
@@ -22,37 +22,37 @@
         <dependency>
             <groupId>fr.insee.trevas</groupId>
             <artifactId>vtl-engine</artifactId>
-            <version>1.9.0</version>
+            <version>1.10.0</version>
         </dependency>
         <dependency>
             <groupId>fr.insee.trevas</groupId>
             <artifactId>vtl-jackson</artifactId>
-            <version>1.9.0</version>
+            <version>1.10.0</version>
         </dependency>
         <dependency>
             <groupId>fr.insee.trevas</groupId>
             <artifactId>vtl-jdbc</artifactId>
-            <version>1.9.0</version>
+            <version>1.10.0</version>
         </dependency>
         <dependency>
             <groupId>fr.insee.trevas</groupId>
             <artifactId>vtl-model</artifactId>
-            <version>1.9.0</version>
+            <version>1.10.0</version>
         </dependency>
         <dependency>
             <groupId>fr.insee.trevas</groupId>
             <artifactId>vtl-parser</artifactId>
-            <version>1.9.0</version>
+            <version>1.10.0</version>
         </dependency>
         <dependency>
             <groupId>fr.insee.trevas</groupId>
             <artifactId>vtl-spark</artifactId>
-            <version>1.9.0</version>
+            <version>1.10.0</version>
         </dependency>
         <dependency>
             <groupId>fr.insee.trevas</groupId>
             <artifactId>vtl-csv</artifactId>
-            <version>1.9.0</version>
+            <version>1.10.0</version>
         </dependency>
         <dependency>
             <groupId>com.fasterxml.jackson.core</groupId>