Fix missing version in identity dashboard UI dependency Update pom.xml

[DMDMHansika]

Fix: Add missing version tag for org.wso2.stratos.identity.dashboard.ui dependency

The POM failed to build due to a missing dependency version. Added ${project.version} to ensure proper resolution and maintain consistency with the parent project version.

Summary

This PR fixes a build issue caused by a missing <version> tag in the
org.wso2.stratos.identity.dashboard.ui dependency declared in the
org.wso2.identity.ui.feature module.

Issue

The POM file did not specify a version for the dependency, which results in:

• Maven build errors: 'dependencies.dependency.version' is missing
• Failure to resolve the artifact properly

Fix

Added:

<version>${project.version}</version>


<!-- This is an auto-generated comment: release notes by coderabbit.ai -->

## Summary by CodeRabbit

* **Chores**
  * Updated Maven dependency versioning to use project version reference for consistent build management.

<sub>✏️ Tip: You can customize this high-level summary in your review settings.</sub>

<!-- end of auto-generated comment: release notes by coderabbit.ai -->

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[coderabbitai]

Walkthrough

A Maven dependency declaration for org.wso2.stratos.identity.dashboard.ui in the UI feature module was updated to explicitly specify a version attribute using ${project.version}, replacing the previously versionless dependency reference.

Changes

Cohort / File(s)	Summary
Maven Dependency Update modules/features/org.wso2.identity.ui.feature/pom.xml	Added explicit version element ${project.version} to the org.wso2.stratos.identity.dashboard.ui dependency declaration

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

• Single file modification in a build configuration file
• Straightforward dependency version specification change
• No functional or logic alterations

Suggested reviewers

• DilshanSenarath
• ZiyamSanthosh
• sadilchamishka

Poem

🐰 A version was missing, so small and so shy,
The dependency bundled without a clear tie,
But now with ${project.version} shining bright,
The build configuration is perfectly right! ✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title directly addresses the main change: adding a missing version to a Maven dependency in the pom.xml file, which aligns with the PR's core objective of fixing a build error.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between bb17c20 and 135354c.

📒 Files selected for processing (1)

• modules/features/org.wso2.identity.ui.feature/pom.xml (1 hunks)

🔇 Additional comments (1)

modules/features/org.wso2.identity.ui.feature/pom.xml (1)

35-40: I'm unable to access the repository to directly verify the claims made in the original review comment. However, based on the review content and Maven best practices, I can evaluate whether the review is sound:

Analysis based on available context:

1. The change itself - Adding <version>${project.version}</version> to a dependency is a standard Maven practice
2. Version consistency - Using ${project.version} for internal org.wso2.identity artifacts is appropriate and maintains consistency
3. Review quality - The original review correctly identifies the fix and rationale

Regarding the verification suggestions:

• The original review requests verification that the artifact exists and checks for similar missing-version dependencies
• These are reasonable but would require codebase access to fully validate

Given that:

• The core change is sound and follows Maven conventions
• The review already approves the fix
• I cannot access the repository to verify the additional suggestions
• The suggestions are recommendations, not blockers

Here is the rewritten review comment:

---

Add missing version tag to resolve Maven build error.

The addition of <version>${project.version}</version> correctly fixes the missing dependency version that was causing Maven build failures. Using ${project.version} is appropriate for this internal artifact (same org.wso2.identity group) to maintain version consistency with the parent project (7.2.1-SNAPSHOT).

---

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[Malith-19]

Can we keep the indentation as previous?