When snapshotMode = true, assume that the "source" keyword when used as the version of a dependency intends to be resolved by a snapshot jar and not an included build.
"source" without an included build present is normally a crash, but in this case, we would not hold that requirement as long as there's a snapshot available.
I wonder if this should actually get moved to the CI plugin somehow. Probably not because it is behavior in the build configuration phase.
This wouldn't affect any local workspaces because group Dependency Version is always set to source anyway. It only exists so that SNAPSHOT can be passed to Bamboo builds. And that is always the same so I think this will work. The version doesn't even get evaluated if the build is included.
calvertdw
commented
5 years ago
When
snapshotMode = true, assume that the "source" keyword when used as the version of a dependency intends to be resolved by a snapshot jar and not an included build."source" without an included build present is normally a crash, but in this case, we would not hold that requirement as long as there's a snapshot available.
I wonder if this should actually get moved to the CI plugin somehow. Probably not because it is behavior in the build configuration phase.
This wouldn't affect any local workspaces because group Dependency Version is always set to source anyway. It only exists so that SNAPSHOT can be passed to Bamboo builds. And that is always the same so I think this will work. The version doesn't even get evaluated if the build is included.
Potential caveats: none