gradle-git-properties | Gradle plugin for git.properties file generation | Plugin library

The problem is that you have multiple Gradle processes that are still holding locks to your files.

You can try running gradle --stop when this happens to stop any daemons that are running in the backgorund (this usually helps).

You can also check the state of your daemons by running gradle --status. For me this outputs:

To make the answer more visible (valid for jhipster 4.x):

for creating a war that can be deployed in an application server use ./gradlew war and for an executable war file, which can be executed via java -jar use ./gradlew bootWar.

The jks was corrupt. I tested the jks with:

What's the [Docker] image you run your job on? I don't see any image: specifications in your .gitlab-ci.yml. Make sure it has npm installed or make sure that your Gradle scripts contains instructions or tasks for installing it. You should probably set nodeInstall property before running the build:

I think you have some confusion over where and how the data is being stored, and in particular when it's available.

I just got hold of this plugin and had a look at it: it supplies a project extension, which you're configuring to specify why extras property to populate, and a task: "generateGitProperties". This task is added as a dependency for the "classes" task, so it's already run once you get to "shadowJar"

The issue is that figuring out the git properties and populating the extra properties only happens when that task is executed, so they're not available when the build is configured, hence the need for the lazy GString shenanigans to pass a lazy value down into the shadowJar configuration that will only be evaluated once shadowJar executes.

You can get hold of the extra properties like this:

When your plugin configures the project in question and applies the com.gorylenko.gradle-git-properties, you will have to configure the extension contributed by the underlying plugin.

Given that this plugin registers an extension of type GitPropertiesPluginExtension, you need to get access to it and then can configure it (code in Java):

It turns out that when running from Idea plugin is not executed - I've changed configuration in Idea to use gradle https://stackoverflow.com/a/48060458/296427 and it works like a charm

the current Cassandra versions are not compatible with jdk10. You'll have to downgrade your java to jdk8.

The problem was running the app from IDE. As the properties are generated on the phase when JAR is assembled, they were not included. Running the application via java -jar artifact.jar or gradle bootRun works without any issues.

Thanks @fateddy for help on resolving the issue.