build-info: API-breaking changes with org.jfrog.buildinfo:build-info-extractor-gradle:latest.release

Describe the bug A clear and concise description of what the bug is.

The gradle-artifactory-plugin doc recommends using the plugin with the latest.release version like this:

buildscript {
  repositories {
    mavenCentral()
  }
  dependencies {
    classpath "org.jfrog.buildinfo:build-info-extractor-gradle:latest.release"
  }
}
apply plugin: "com.jfrog.artifactory"

Further down the page, the doc shows a template for the plugin configuration that begins like this:

artifactory {
  +contextUrl = 'http://repo.myorg.com/artifactory'  

Since the publication of version 5.0.0 on 2023-06-29 (today), we now have a strange behavior with an error like this:

> Could not set unknown property 'contextUrl' for extension 'artifactory' of type org.jfrog.gradle.plugin.artifactory.config.ArtifactoryPluginConvention.

This occurs in a gradle script like this:

ext {
   jpl_imce_artifactory_url = "...'
}
artifactory {
  contextUrl = jpl_imce_artifactory_url // Gradle reports an error at this line.
  ...
}

It seems that version 5.0.0 introduces an incompatible configuration paradigm that makes the current documentation based on version 4.x obsolete.

Furthermore, I cannot even find any source code corresponding to org.jfrog.gradle.plugin.artifactory.config.ArtifactoryPluginConvention

To Reproduce Steps to reproduce the behavior

See above.

Expected behavior A clear and concise description of what you expected to happen.

Version 5.0.0 should be backwards compatible with previous versions of the gradle artifactory plugin.

Screenshots If applicable, add screenshots to help explain your problem.

Versions

  • Extractor version:
  • Operating system:
  • Artifactory Version:

Additional context Add any other context about the problem here.

About this issue

  • Original URL
  • State: open
  • Created a year ago
  • Comments: 23 (7 by maintainers)

Commits related to this issue

Most upvoted comments

All - We wrongly assumed people were using the latest 4 version (4+) as part of their Gradle scripts. Let us check internally the best way to move forward and share an update here.

@eyalbe4 Since the API-breaking changes are intentional in Version 5, shouldn’t this be documented?

Until this happens, the current documentation for the plugin version, latest.release, has become factually wrong.