Dependency dynamic versioning

Help/Discuss
1

I have a library which I update with minor changes regularly. I’d like to use dynamic versioning in a project that depends on it.

The highest available version at the moment is 1.13, however if I set the version to 1.+, it only uses 1.11. If I directly specify 1.13 than that version is used. Isn’t 1.+ supposed to bind to the highest available version (if still starts with 1.) or I completely miss something? (The gradle docs on how dynamic versions can be defined is really short-spoken.)

The project file and setup with

The content of maven-metadata.xml of the referenced library:

<?xml version="1.0" encoding="UTF-8"?>
<metadata>
  <groupId>alf.stokes</groupId>
  <artifactId>swing-utilities</artifactId>
  <versioning>
    <release>1.13</release>
    <versions>
      <version>1.0</version>
      <version>1.1</version>
      <version>1.2</version>
      <version>1.3</version>
      <version>1.4</version>
      <version>1.5</version>
      <version>1.6</version>
      <version>1.7</version>
      <version>1.8</version>
      <version>1.9</version>
      <version>1.10</version>
      <version>1.11</version>
      <version>1.12</version>
      <version>1.13</version>
    </versions>
    <lastUpdated>20150924075951</lastUpdated>
  </versioning>
</metadata>

Thanks for the help in advance!

1 Like
2

Still hoping for an answer :slight_smile:

1 Like