Dears,
I am deploying a new module developed with the SDK.
I need to set the proper build number, based on the build timestamp.
Following the tips of your user guides and the forum, I always get “b0” after compiling it.
The code in the module pom file is:
<properties>
<ignition-platform-version>8.0.7</ignition-platform-version>
<ignition-sdk-version>${ignition-platform-version}</ignition-sdk-version>
<module-name> KPI</module-name>
<module-description>A module that provides the implementation of new KPI functionalities</module-description>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
<project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding>
<timestamp>${maven.build.timestamp}</timestamp>
<maven.build.timestamp.format>yyyyMMddHH</maven.build.timestamp.format>
<buildNumber>${maven.build.timestamp}</buildNumber>
</properties>
Where am I wrong?
Thank you so much.
Best regards,
Andrea
You would need to include the build number in the version you specify when configuring the ignition-maven-plugin in your build module.
If you copied from the examples it probably just looks like this:
<moduleVersion>${project.version}</moduleVersion>
You would need to modify this so it is in the format major.minor.rev.build
.
Hi Kevin,
thank you for the reply.
I did it, but the build number results always 0.
In the configuration tag (in the buid pom file):
<moduleId>com.xxx.ignition.kernel.kpi</moduleId>
<moduleName>${module-name}</moduleName>
<moduleDescription>${module-description}</moduleDescription>
<moduleVersion>${project.version}</moduleVersion>
<requiredIgnitionVersion>${ignition-platform-version}</requiredIgnitionVersion>
<requiredFrameworkVersion>8</requiredFrameworkVersion>
<licenseFile>license.html</licenseFile>
<documentationFile>doc/index.html</documentationFile>
I copied it from the examples, where the version is:
<version>1.0.0-SNAPSHOT</version>
Let me know if I can give you further details.
Thank you so much!
Well what I’m saying is that using ${project.version}
is not sufficient. You need to change it to use your custom buildNumber
property somehow.
Thank you Kevin, I understood. Now the build number is as expected.
Best,
Andrea