Skip to content

[Improve] Replace ${revision} with ${project.version} in artifact paths #351

Description

@hingu-8103

Feature Description (功能描述)

Purpose

Replace ${revision} with ${project.version} in artifact file paths and <finalName> declarations to fix broken builds after running mvn versions:set.

Background

The root POM uses ${revision} as the version property. However, two files reference ${revision} directly in file path strings and <finalName> When mvn versions:set -DnewVersion=X.Y.Z is run, it updates <version> tags and occurences of ${version} with newVersion but not in the strings and <finalName>— causing the copy tasks to look for JARs with the old version in their filename, breaking the build.

Problems

  • mvn versions:set breaks the build — copy tasks reference artifacts that no longer exist.
  • Risk of version drift between ${revision} and the actual built artifact filenames.

Proposed Fix

In computer/computer-dist/pom.xml, replace the two ${revision} occurrences in the <copy> file path attributes with ${project.version}.

In computer/computer-k8s-operator/pom.xml, replace the ${revision} occurrence in the <finalName> declaration with ${project.version}.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions