sarhanm/gradle-versioner

Issues

• branchEnvName is not used to read Environment variable

  #33 opened 6 years ago
  2

• Version range resolution is brittle

  #32 opened 6 years ago
  0

• lightweight tags are not supported

  #31 opened 6 years ago
  1

• Pom generation should include the resolved versions instead of 'auto'

  #27 opened 8 years ago
  0

• Version-resolver fails if no manifest is defined

  #25 opened 8 years ago
  0

• stackoverflow error when resolving versions

  #24 opened 8 years ago
  0

• Configurations not always participate in resolution

  #22 opened 8 years ago
  0

• Versions explicitly marked in the current build.gradle don't always override gradle resolution

  #20 opened 8 years ago
  0

• Omit snapshot on master branch

  #18 opened 9 years ago
  2

• Setting project.version to object breaks lots of plugins

  #15 opened 9 years ago
  0

• Hotfix values are incorrect

  #14 opened 9 years ago
  0

• Resolver doesn't honor --refresh-dependencies

  #11 opened 9 years ago
  0

• Not placing the code execution in afterEvaluate is causing early evaluation of gradle

  #9 opened 10 years ago
  6

• Build stuck on branch named "release/hotfix"

  #7 opened 9 years ago
  1

• Version resolution for auto and version ranges broke with gradle 2.2.1 update

  #5 opened 10 years ago
  0

• potential bug: hotfix point versions are not based on commonHotfixBranch

  #4 opened 10 years ago
  0

• feature request: make hotfix 4-point versions optional

  #3 opened 10 years ago
  0

• version resolver is not applied to build script dependencies

  #2 opened 6 years ago
  3

• Omit branch metadata on solid branch

  #1 opened 10 years ago
  2