Skip to content

Recognize service metadata update in plugin-core and download fresh API #13

@vsbogd

Description

@vsbogd

gradle-plugin and maven-plugin doesn't check for API update:

  • maven-plugin gets API on each build which is ineffective;
  • gradle-plugin because of Gradle behavior doesn't update API after downloading for the first time because file is already in filesystem.

This behavior could be improved by the following way:

  • plugin-core keeps the service metadata hash in the build directory;
  • plugin-core checks the metadata was not changed since the previous run comparing the local hash with one in Registry contract (it can be done once per day like maven logic of artifacts updating);
  • if the metadata hash is changed then plugin-core downloads new version of API;
  • gradle-plugin to be modified to check metadata update on each run;
  • maven-plugin is expected to work with new logic correctly without any modifications.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions