[ 
https://issues.apache.org/jira/browse/PARQUET-1506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16751083#comment-16751083
 ] 

ASF GitHub Bot commented on PARQUET-1506:
-----------------------------------------

gszadovszky commented on pull request #600: [PARQUET-1506] Migrate 
maven-thrift-plugin to thrift-maven-plugin
URL: https://github.com/apache/parquet-mr/pull/600
 
 
   
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Migrate from maven-thrift-plugin to thrift-maven-plugin
> -------------------------------------------------------
>
>                 Key: PARQUET-1506
>                 URL: https://issues.apache.org/jira/browse/PARQUET-1506
>             Project: Parquet
>          Issue Type: Improvement
>          Components: parquet-mr
>    Affects Versions: 1.10.0
>            Reporter: Fokko Driesprong
>            Assignee: Fokko Driesprong
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.11.0
>
>
> Hi guys,
> I'd would like to migrate from maven-thrift-plugin to thrift-maven-plugin.
> The current one that we use is rather old.
> maven-thrift-plugin (Aug 13, 2013) 
> https://mvnrepository.com/artifact/org.apache.thrift.tools/maven-thrift-plugin/0.1.11
> thrift-maven-plugin (Jan 18, 2017) 
> https://mvnrepository.com/artifact/org.apache.thrift/thrift-maven-plugin/0.10.0
> The maven-thrift-plugin is the old one which has been migrated to the ASF
> and continued as thrift-maven-plugin:
> https://issues.apache.org/jira/browse/THRIFT-4083
> I'm investigating bumping the thift version to make it Java 11 compatible. 
> But having a newer version of the maven plugin is a requirement:
> https://issues.apache.org/jira/browse/THRIFT-4083



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to