[
https://issues.apache.org/jira/browse/THRIFT-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12921555#action_12921555
]
Anthony Molinaro commented on THRIFT-6:
---------------------------------------
Yeah, I wrote my opinion on this on the dev list, so I'm sure you all saw it,
but I do think having a single unified version is worth it. For most people it
means they'll have had to run configure one time to be able to build. But
since most people will probably follow the download, untar, ./configure && make
recipe they probably already do this anyway?
One other alternative which I don't necessarily agree with is to completely
split thrift up into completely separate pieces, versioned separately. But
the compiler ends up being the tricky bit there, in that usually a version of
the generated code matches the runtime library for a language. We could try to
split the compiler into a runtime component and a bunch of dynamically loaded
modules, then you package a language plugin for thrift which contains the
generator library, plus the runtime library. That would be neat as you could
release new languages without central control, but it would suck in that it'd
be hard to test all combinations (it's already hard when they are all next to
each other, now imagine they are spread out over 10 different repositories and
all versioned separately).
Anyway more discussion is always welcome before we commit to one or the other.
> 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
> Assignee: Roger Meier
> Attachments:
> v1-0001-THRIFT-6.-Add-a-Makefile-rule-to-print-the-version-f.patch
>
>
> 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.
