[ 
https://issues.apache.org/jira/browse/DRILL-6916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vitalii Diravka updated DRILL-6916:
-----------------------------------
    Summary: Fix extraneous "${project.basedir}/src/site/resources/repo/" 
directory appearance  (was: "${project.basedir}/src/site/resources/repo/" 
extraneous directory in Drill sources)

> Fix extraneous "${project.basedir}/src/site/resources/repo/" directory 
> appearance
> ---------------------------------------------------------------------------------
>
>                 Key: DRILL-6916
>                 URL: https://issues.apache.org/jira/browse/DRILL-6916
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Storage - HBase, Tools, Build & Test
>    Affects Versions: 1.15.0
>            Reporter: Vitalii Diravka
>            Assignee: Vitalii Diravka
>            Priority: Minor
>             Fix For: 1.15.0
>
>
> After upgrade HBase lib (in scope of DRILL-6349) in Drill project sources 
> root directory the extraneous directory can be created in the process of 
> {{mvn clean install -DskipTests -pl contrib/storage-hbase/}}
>  It is related to absent {{maven-metadata.xml}} file in 
> {{org.glassfish:javax.el}} transitive dependency from HBase lib.
>  See info from {{mvn release:prepare -X}}:
> {noformat}
> [INFO] [DEBUG] Failure to find org.glassfish:javax.el/maven-metadata.xml in 
> file:${project.basedir}/src/site/resources/repo was cached in the local 
> repository, resolution will not be reattempted until the update interval of 
> project.local has elapsed or updates are forced{noformat}
> So it can be easily reproduced with removing {{org.glassfish:javax.el}} from 
> local maven repo:
> {noformat}
> ~/.m2/repository/org/glassfish/javax.el{noformat}
> and making Drill build for HBase package:
> {noformat}
> mvn clean install -DskipTests -pl contrib/storage-hbase/{noformat}
> Solution: update HBase lib to the latest 2.1.1 version, it hasn't this issue.



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

Reply via email to