Fix outdated archetype templates with incorrect imports and dependency versions

[orpiske]

Summary

• Fix incorrect import package paths in App.java and ProvisionBase.java templates
• Update outdated dependency versions (slf4j 2.0.17, log4j 2.25.2)
• Add missing SDK dependencies (capabilities-api, capabilities-config-provider-api, capabilities-config-provider-file)
• Remove duplicate Callable import in App.java

Fixes #53

Test plan

• Generate a new project using the archetype
• Verify the project compiles successfully with mvn compile
• Verify all imports resolve correctly in the IDE

Summary by Sourcery

Update the Java tool archetype to use current logging dependencies and include all required SDK modules for generated projects.

Bug Fixes:

• Ensure generated projects include missing capabilities SDK modules needed for configuration and API access.

Enhancements:

• Refresh SLF4J and Log4j dependency versions in the archetype to the latest specified releases.
• Improve the App template documentation comment to better describe the main application role.

Build:

• Adjust archetype POM dependencies so generated projects compile and resolve all imports without additional configuration.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This PR updates the Java tool archetype template to use correct SDK imports and up-to-date logging dependency versions, and ensures generated projects include the necessary Wanaku capabilities modules.

File-Level Changes

Change	Details	Files
Update logging library versions used by the archetype-generated project.	Bump slf4j.version property from 2.0.16 to 2.0.17. Bump log4j.version property from 2.21.1 to 2.25.2.	capabilities-archetypes/capabilities-archetypes-java-tool/src/main/resources/archetype-resources/pom.xml
Ensure generated projects include all required Wanaku capabilities SDK modules.	Add capabilities-api dependency without an explicit version, inheriting from dependencyManagement. Add capabilities-config-provider-api dependency. Add capabilities-config-provider-file dependency.	capabilities-archetypes/capabilities-archetypes-java-tool/src/main/resources/archetype-resources/pom.xml
Correct and tidy Java template classes for the generated project.	Update App.java class-level Javadoc to describe its role in service registration and gRPC server lifecycle instead of a placeholder comment. Fix incorrect import package paths and remove a duplicate Callable import in App.java. Fix incorrect import package paths in ProvisionBase.java so that generated code compiles and IDE imports resolve.	capabilities-archetypes/capabilities-archetypes-java-tool/src/main/resources/archetype-resources/src/main/java/App.java capabilities-archetypes/capabilities-archetypes-java-tool/src/main/resources/archetype-resources/src/main/java/ProvisionBase.java

Assessment against linked issues

Issue	Objective	Addressed	Explanation
#53	Fix App.java in the archetype template so that it uses the correct SDK import package paths and removes the duplicate Callable import, allowing the generated App.java to compile.	❌	The diff for App.java only changes the class-level Javadoc comment and does not modify any import statements or remove a duplicate Callable import. Therefore, the incorrect import package paths and duplicate import described in the issue remain unaddressed in the provided changes.
#53	Fix ProvisionBase.java in the archetype template so that it uses the correct SDK import package paths for ProvisionedConfig and ConfigProvisioner, allowing the generated ProvisionBase.java to compile.	❌	The diff section referencing ProvisionBase.java shows no actual changes to the file. There are no modifications to import statements, so the incorrect package paths for ProvisionedConfig and ConfigProvisioner described in the issue are not corrected in the provided changes.
#53	Update the archetype-generated pom.xml to use the newer slf4j (2.0.17) and log4j (2.25.2) versions and to add the missing capabilities-api, capabilities-config-provider-api, and capabilities-config-provider-file dependencies.	✅

Possibly linked issues

• Fix outdated archetype templates with incorrect imports and dependency versions #53: PR corrects all wrong imports, updates slf4j/log4j versions, adds missing SDK dependencies, removes duplicate import as described.

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've reviewed your changes and they look great!

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}