[
https://issues.apache.org/jira/browse/HDDS-4671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hui Fei updated HDDS-4671:
--------------------------
Description:
In acceptance.sh, blockade.sh & kubernetes.sh
I see
{quote}
OZONE_VERSION=$(grep "<ozone.version>" "pom.xml" | sed 's/<[^>]*>//g'| sed
's/^[ \t]*//')
{quote}
It seems that using mvn to get ozone.version is more clear.
{quote}
OZONE_VERSION=$(mvn help:evaluate -Dexpression=ozone.version -q -DforceStdout)
{quote}
was:
Run the following command to set new version and build
{code:java}
mvn versions:set -DnewVersion=1.1.0 && mvn versions:commit && mvn clean package
-DskipTests -Dmaven.javadoc.skip=true
{code}
ozone.version does not change, and building fails, failing message is following
{quote}
[INFO] Compiling 1 proto file(s) to
/Users/fermi/projects/hadoop-ozone/hadoop-hdds/interface-admin/target/generated-sources/java
[ERROR] PROTOC FAILED: ScmAdminProtocol.proto:245:12: "NodeOperationalState" is
not defined.
[ERROR]
/Users/fermi/projects/hadoop-ozone/hadoop-hdds/interface-admin/src/main/proto/ScmAdminProtocol.proto
[0:0]: ScmAdminProtocol.proto:245:12: "NodeOperationalState" is not defined.
{quote}
> Use mvn to get ozone.version instead of complex shell commands
> ---------------------------------------------------------------
>
> Key: HDDS-4671
> URL: https://issues.apache.org/jira/browse/HDDS-4671
> Project: Hadoop Distributed Data Store
> Issue Type: Improvement
> Components: build
> Affects Versions: 1.0.0
> Reporter: Hui Fei
> Priority: Major
> Labels: pull-request-available
>
> In acceptance.sh, blockade.sh & kubernetes.sh
> I see
> {quote}
> OZONE_VERSION=$(grep "<ozone.version>" "pom.xml" | sed 's/<[^>]*>//g'| sed
> 's/^[ \t]*//')
> {quote}
> It seems that using mvn to get ozone.version is more clear.
> {quote}
> OZONE_VERSION=$(mvn help:evaluate -Dexpression=ozone.version -q -DforceStdout)
> {quote}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
