Skip to content

Releases: saantiaguilera/gradle-api-easy_publish

v4.0.0

19 Oct 15:53
Compare
Choose a tag to compare

CHANGELOG

  • Start using maven-publish plugin
  • Support flavors / buildtypes
  • Refactor of code
  • Use of group/name/version of gradle project for groupId:artifactId:version

v3.0.0

26 Jun 20:31
Compare
Choose a tag to compare

CHANGELOG

  • No need to add a publish order. We are making needed tasks depend from the publishing so we can publish them in any possible order
  • The DefaultMavenPom is only parsing me the default configurations and other relevant ones. Im parsing the pom configurations on my own now adding the needed
  • Added bintray missing attributes:
    • SyncToMavenCentral (This includes ossUser/ossPassword/ossClose)
    • UserOrganization
    • GPG support
    • PackageLabels
    • Package/Version Description
    • WebsiteUrl
    • Override
    • PublicDownloadNumbers

v2.0.2

24 Jun 05:49
Compare
Choose a tag to compare

CHANGELOG

  • When creating for the first time a package in bintray, if using licenses it will add the module license to the package
  • Generated dependencies of the pom are changed correctly if they are local ones
  • Added publishOrder to the global configuration since we cant know the order (and one with local dependencies might go first without being its dependants resolved)

v2.0.1

24 Jun 03:43
Compare
Choose a tag to compare

CHANGELOG

  • Defers validation of mandatory values (for example bintrayUser) to the moment the task is generated (before it was right after the module plugin is applied). It improves configurability since it can be done at any given point of the build.gradle evaluation/configuring phase (instead of before starting to configure the modules)
  • Improves logs in case of missing mandatory values

v2.0.0

23 Jun 17:57
Compare
Choose a tag to compare

CHANGELOG

  • Global configurations. For avoiding boilerplating
  • Scope configurations. You can still specify for each lib different values. This always has higher priority than global configurations
  • Artifact inference. If no artifact specified, it will use the module name
  • Artifact mapping. You can apply a global map to configure all modules->artifacts instead of doing one by one
  • Local dependencies inference. If local dependencies are between modules, it will change them to the release its being done. Note that if a map is also specified, it will use the map artifact instead of the module name (as it is per default)

v1.0.1

23 Jun 06:26
Compare
Choose a tag to compare

CHANGELOG

  • Uses this plugin to publish this plugin (it auto consumes itself for publishing)

v1.0.0

23 Jun 06:24
Compare
Choose a tag to compare

CHANGELOG

  • Adds plugin
  • Adds JAR/AAR feature
  • Adds multi-artifact publishing
  • Adds license
  • Adds group/artifact/version
  • Adds local inter-dependencies between artifacts handling