[Packaging] Stop to refer java/pom.xml to get version information

[asfimport]

#3096 (comment)

I want to stop the current version sharing style. (Referring java/pom.xml from C++, Python, C, Ruby, ....)
It introduces complexity. For example, we generates version.rb dynamically to create a Ruby package: https://github.com/apache/arrow/blob/master/ruby/red-arrow/version.rb

I think that we can just replace all versions in cpp/CMakeLists.txt, python/setup.py, c_glib/configure.ac, ruby/*/lib/*/version.rb, rust/Cargo.toml, ... by sed in the release process.

Reporter: Kouhei Sutou / @kou
Assignee: Kouhei Sutou / @kou

PRs and other links:

• GitHub Pull Request #3259

_{Note: This issue was originally created as ARROW-3938. Please see the migration documentation for further details.}

[asfimport]

Kouhei Sutou / @kou:
Comment from @wesm #3096 (comment)

One complexity is that we need to be able to produce development version numbers using setuptools_scm when building the Python wheels.

[asfimport]

Krisztian Szucs / @kszucs:
Ideally We should generate version numbers based on VCS tags for all implementations.

[asfimport]

Wes McKinney / @wesm:
Is this doable for 0.12?

[asfimport]

Kouhei Sutou / @kou:
Yes.
I'll be able to work on this week or the next week.

[asfimport]

Wes McKinney / @wesm:
Issue resolved by pull request 3259
#3259