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

koert kuipers edited comment on PARQUET-178 at 2/5/15 6:32 PM:
---------------------------------------------------------------

they caused trouble for me because the same files are also in the slf4j-api 
jar. i was using sbt assembly to build a super-jar (jar with all compile 
dependencies included) and it threw an error because it didn't know how to 
handle these duplicates.

also besides super-jars, people in general might include their own slf4j 
version. i know we do. these files might potentially provide the wrong 
information if they clobber the ones included with a slf4j dependency? not 
sure...


was (Author: koert):
they caused trouble for me because the same files are also in the slf4j-api 
jar. i was using sbt assembly to build a super-jar (jar with all compile 
dependencies included) and it threw an error because it didn't know how to 
handle these duplicates.

also people might include their own slf4j version. i know we do. these files 
might potentially provide the wrong information if they clobber the ones 
included with a slf4j dependency? not sure...

> META-INF for slf4j should not be in parquet-format jar
> ------------------------------------------------------
>
>                 Key: PARQUET-178
>                 URL: https://issues.apache.org/jira/browse/PARQUET-178
>             Project: Parquet
>          Issue Type: Bug
>          Components: parquet-format
>    Affects Versions: 1.6.0rc2
>            Reporter: koert kuipers
>            Priority: Minor
>
> {noformat}
> $ jar tf parquet-format-2.2.0-rc1.jar  | grep org\\.slf
> META-INF/maven/org.slf4j/
> META-INF/maven/org.slf4j/slf4j-api/
> META-INF/maven/org.slf4j/slf4j-api/pom.xml
> META-INF/maven/org.slf4j/slf4j-api/pom.properties
> {noformat}
> It is not clear to me why these are here. I suspect they should not be.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to