gradle-info-plugin
gradle-info-plugin copied to clipboard
nebula-plugins
Plugin to gather information about the environment
It is unlikely that the original intent was to expose getters such as `getBUILT_BY_PROPERTY()`, so change those properties to `public` fields, for the benefit of a clearer API, and more...
# Summary Missing up-to-date checks for Jar tasks: when data collected by `nebula.info` changes (e.g. Git commit), it should invalidate any previous jar tasks, instead of reusing the old task...
for example, if not need resolve entry
Updated svnkit version to '1.10.3' and added "org.lz4:lz4-java:1.4.1" dependency in the lockfiles, to support new version of svnkit. Signed-off-by: odidev
This report gets pretty expensive to compute and store on complex projects.
This commit changes the format of the Build-Date in the jar manifest to be formatted in ISO 8601 including the timezone offset. Additionally, for convenience, the format used to represent...
If the `P4CONFIG` environment variable is defined (for use with Perforce) I get a Gradle build error (see below for details...). Looking at PerforceScmProvider.groovy it seems to be related to...
For info-props Plugin use baseName instead of archivesBaseName. baseName is specific to war task. It defaults to archivesBaseName so there should not compatibility problems.
We have been using Gradle v 4.10.3 for a while. Our projects are referring to nebula.info plugin with v 4.0.3 and we did not have any issues. Suddenly our builds...
Branch field contains commit id for Git builds on Jenkins. If the same build executed locally branch id is added correctly to the manifest file.
Metadata
Owner
Metadata
Plugin to gather information about the environment