[
https://issues.apache.org/jira/browse/ACCUMULO-2197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13881524#comment-13881524
]
Christopher Tubbs commented on ACCUMULO-2197:
---------------------------------------------
[~elserj]: While sysadmins may wish to build Accumulo, I don't see that as a
sysadmin responsibility. Technically speaking, it's probably a "package
maintainer" responsibility... and package maintainers typically have the same
dependency environment as a developer, because they typically must build
everything from source.
Ideally, it'd be nice to provide SRPMs which include generated source, for
sysadmins to build an RPM from. If they're building from raw source, I don't
see why their environment should be any different than any other developer,
though.
On the other hand, I do think that there'd be some merit to separating out the
thrift build so that it produces versioned release artifacts, rather than
version-controlling thrift IDL files. This could/should be done as part of
ACCUMULO-756, which I've been meaning to revisit soon.
> Building RPMs requires thrift profile to be active
> --------------------------------------------------
>
> Key: ACCUMULO-2197
> URL: https://issues.apache.org/jira/browse/ACCUMULO-2197
> Project: Accumulo
> Issue Type: Bug
> Components: build
> Affects Versions: 1.5.0
> Reporter: Josh Elser
> Assignee: Josh Elser
> Fix For: 1.5.1, 1.6.0
>
>
> The generated sources (cpp, rb, py) for the proxy are only generated when the
> thrift maven profile is activated. An RPM assembly expects these files to be
> present. Thus, the following fails:
> {code}
> mvn package -Passemble,rpm -DskipTests
> {code}
> We should probably just include the gen-* variants under src/generated (or
> similar), commit them to the repository, and let the thrift profile
> regenerate those files as necessary.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
