Add API to expose generated properties about gradle-git-properties HOT 6 CLOSED

This feature should be supported in the next release v1.5.0. Specifically, extProperty config key will be able to be configured to expose the properties map under project.ext

from gradle-git-properties.

Closing because the feature is now available in v1.5.0
Please open new ticket for other requests. Thanks.

from gradle-git-properties.

Thanks for the suggestion. I'm thinking about exposing a Map as task output so the properties can be accessed as generateGitProperties.properties['git.commit.id.abbrev']

BTW because of the UP-TO-DATE check mechanism of Gradle, sometimes, the task will not be executed and so the Map would not be exposed, you will have to force task execution with

generateGitProperties.outputs.upToDateWhen { false }

And of course you will still need

dependsOn tasks.generateGitProperties

to make sure generateGitProperties to be executed before your logic

I'm also thinking about adding generateGitPropertiesFile config for the users who need the properties (but not the generated git.properties file). But it would complicate the way up-to-date check works for the plugin.

What do you think?

from gradle-git-properties.

I don't see any benefits in having just exposed properties without the file. Gained performance boost will be negligible but it will introduce more complicated code.

from gradle-git-properties.

Please also add a task to display all generated properties.

from gradle-git-properties.

@sdavids If it is for debugging purpose, I would suggest to use plugin version 1.5 with "--debug" option to display the generated map (see https://github.com/n0mer/gradle-git-properties/blob/master/src/main/groovy/com/gorylenko/GenerateGitPropertiesTask.groovy). If it is not for the debugging, why do you think the extProperty config will not sufficient for the job?

from gradle-git-properties.