[AURON #1434] Use Maven-native version extraction instead of xmllint for better portability

[merrily01]

Which issue does this PR close?

Closes #1434 .

Rationale for this change

Previously, the build script relied on xmllint to parse pom.xml and extract
project.version, which caused build failures in environments where xmllint
is not available (e.g., GitHub Actions or minimal Docker images).

This change replaces it with:

  ./build/mvn help:evaluate -N -Dexpression=project.version -Pspark-${SPARK_VER} -q -DforceStdout

This approach uses Maven’s built-in model evaluation and works consistently
across platforms without additional dependencies.

What changes are included in this PR?

Are there any user-facing changes?

How was this patch tested?

[ShreyeshArangath]

Nice!

[slfan1989]

LGTM +1

[wForget]

Thanks @merrily01

[merrily01]

Merged. Thanks for the review @ShreyeshArangath @slfan1989 @wForget

[guixiaowen]

@merrily01 me Errors during compilation after merging the code are shown in the figure.

The built file information is

auron-build-info.properties.txt

The build command is: ./auron-build.sh --pre --sparkver 3.5 --scalaver 2.12 -DskipBuildNative -Djansi.passthrough=true -s /Users/didi/.m3/settings.xml -Dmaven

[merrily01]

@merrily01 me Errors during compilation after merging the code are shown in the figure.

The built file information is

auron-build-info.properties.txt

The build command is: ./auron-build.sh --pre --sparkver 3.5 --scalaver 2.12 -DskipBuildNative -Djansi.passthrough=true -s /Users/didi/.m3/settings.xml -Dmaven

It looks like the issue comes from local Maven environment？（probably related to the HTTP repo blocking in your settings.xml）

Could you please try running the same command with a standard Maven setup (e.g., using ~/.m2/settings.xml)?

I just verified that and works fine on my side.

[guixiaowen]

@merrily01 me Errors during compilation after merging the code are shown in the figure.
The built file information is
auron-build-info.properties.txt
The build command is: ./auron-build.sh --pre --sparkver 3.5 --scalaver 2.12 -DskipBuildNative -Djansi.passthrough=true -s /Users/didi/.m3/settings.xml -Dmaven

It looks like the issue comes from local Maven environment？（probably related to the HTTP repo blocking in your settings.xml）

Could you please try running the same command with a standard Maven setup (e.g., using ~/.m2/settings.xml)?

I just verified that and works fine on my side.

@merrily01 Thank you very much for the reply. I'll take another look. Thanks!