Version always comes from VERSION_NAME about gradle-maven-publish-plugin

[vanniktech]

Yep sounds about right. I personally haven't had a user case for taking the project.version.

[benasher44]

In some of the IntelliJ project templates, project.version comes preset, which is how our team got to using/relying on it. Do you think it could make sense to accommodate that in this plugin somehow? Depending on your CI setup, there are good reasons to specify your version at configure time in gradle code.

[vanniktech]

Yeah. I'm thinking if project.version is set take it, otherwise VERSION_NAME. What do you think @gabrielittner ?

[gabrielittner]

We could also just use project.version when configuring the pom. When the plugin is applied we immediately set project.version to VERSION_NAME https://github.com/vanniktech/gradle-maven-publish-plugin/blob/master/src/main/kotlin/com/vanniktech/maven/publish/BaseMavenPublishPlugin.kt#L27
If we continue using project.version after that, instead of reading VERSION_NAME again it becomes overridable in build file.

[vanniktech]

Then let's do that.

[gabrielittner]

@benasher44 Your overridden project.version will be used in 0.10.0.

[benasher44]

Thanks!!