I guess the scenario is pretty well covered by this bug and parquet-180 - once the build uses the published maven artifacts, the installed copy of Thrift on a user's machine shouldn't matter. If there is something that these two bugs wouldn't cover though, I'm happy to open a new one, though.
On Tue, Mar 10, 2015 at 7:40 PM, Ryan Blue (JIRA) <[email protected]> wrote: > > [ > https://issues.apache.org/jira/browse/PARQUET-127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14355953#comment-14355953 > ] > > Ryan Blue commented on PARQUET-127: > ----------------------------------- > > Hi [~nealsid], could you open an issue for your problem? This one is about > using the thrift maven plugin once it is generally available. > > > Use published Thrift plugin/artifact > > ------------------------------------ > > > > Key: PARQUET-127 > > URL: https://issues.apache.org/jira/browse/PARQUET-127 > > Project: Parquet > > Issue Type: Improvement > > Components: parquet-mr > > Reporter: Frank Austin Nothaft > > Assignee: Jake Farrell > > Priority: Minor > > > > Thrift is now publishing the [Thrift tools| > https://issues.apache.org/jira/browse/THRIFT-1536] to Maven Central. We > should move Parquet to depend on the Maven Central artifact instead of the > artifact published in the Twitter repo. Also, we should depend on the Maven > libthrift artifact instead of requiring users to have libthrift installed. > > > > -- > This message was sent by Atlassian JIRA > (v6.3.4#6332) >
