[
https://issues.apache.org/jira/browse/THRIFT-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12916772#action_12916772
]
Roger Meier commented on THRIFT-6:
----------------------------------
existing Thrift Library Version defines:
{code}
$ grep -r "0\.6" * | grep -v .svn
configure.ac:AC_INIT([thrift], [0.6.0-dev])
lib/rb/Rakefile: p.version = "0.6.0"
{code}
other candidates:
{code}
lib/py/setup.py: version = '0.1',
lib/perl/lib/Thrift.pm:our $VERSION = '0.1';
lib/csharp/ThriftMSBuildTask/Properties/AssemblyInfo.cs:[assembly:
AssemblyVersion("1.0.0.0")]
lib/hs/Thrift.cabal:Version: 0.2.0
{code}
How to bring these things into a release?
Which languages are missing here and not covered via VERSION define from
configure.ac?
> Thrift libraries and compiler lack version number
> -------------------------------------------------
>
> Key: THRIFT-6
> URL: https://issues.apache.org/jira/browse/THRIFT-6
> Project: Thrift
> Issue Type: Bug
> Reporter: Bryan Duxbury
>
> Right now it's impossible to tell which version of Thrift you have installed.
> If you're depending on features that have recently been added (and that
> subtly don't exist), you can spend a lot of time chasing your tail trying to
> figure out what the problem is.
> This may be something that has to be implemented piecemeal on each client
> library (ruby gem, java classes, etc). Thoughts?
> While we're at it, let's add a --version switch or something to the compiler
> so you know what version of stuff you're actually generating.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
