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

Travis Crawford commented on HCATALOG-132:
------------------------------------------

I updated that branch to rewrite the "hcatalog" pom file for "hcatalog-core" 
and "hcatalog-server-extensions". Now publishing locally we see all the 
expected jars:

However, looking in the pom files they seem to have a lot more than should be 
in there. I think there's an opportunity to rework the ivy dependencies and 
really trim that down. For example, we depend on "datanucleus-core" but really 
we should be getting that transitively from Hive.

{code}
TW-MBP13-TCrawford:hcatalog travis$ find ~/.m2/repository/org/apache/hcatalog*
/Users/travis/.m2/repository/org/apache/hcatalog
/Users/travis/.m2/repository/org/apache/hcatalog/hcatalog
/Users/travis/.m2/repository/org/apache/hcatalog/hcatalog/0.5.0-dev
/Users/travis/.m2/repository/org/apache/hcatalog/hcatalog/0.5.0-dev/hcatalog-0.5.0-dev.jar
/Users/travis/.m2/repository/org/apache/hcatalog/hcatalog/0.5.0-dev/hcatalog-0.5.0-dev.jar.asc
/Users/travis/.m2/repository/org/apache/hcatalog/hcatalog/0.5.0-dev/hcatalog-0.5.0-dev.pom
/Users/travis/.m2/repository/org/apache/hcatalog/hcatalog/0.5.0-dev/hcatalog-0.5.0-dev.pom.asc
/Users/travis/.m2/repository/org/apache/hcatalog/hcatalog/maven-metadata-local.xml
/Users/travis/.m2/repository/org/apache/hcatalog/hcatalog-core
/Users/travis/.m2/repository/org/apache/hcatalog/hcatalog-core/0.5.0-dev
/Users/travis/.m2/repository/org/apache/hcatalog/hcatalog-core/0.5.0-dev/hcatalog-core-0.5.0-dev.jar
/Users/travis/.m2/repository/org/apache/hcatalog/hcatalog-core/0.5.0-dev/hcatalog-core-0.5.0-dev.jar.asc
/Users/travis/.m2/repository/org/apache/hcatalog/hcatalog-core/0.5.0-dev/hcatalog-core-0.5.0-dev.pom
/Users/travis/.m2/repository/org/apache/hcatalog/hcatalog-core/0.5.0-dev/hcatalog-core-0.5.0-dev.pom.asc
/Users/travis/.m2/repository/org/apache/hcatalog/hcatalog-core/maven-metadata-local.xml
/Users/travis/.m2/repository/org/apache/hcatalog/hcatalog-pig-adapter
/Users/travis/.m2/repository/org/apache/hcatalog/hcatalog-pig-adapter/0.5.0-dev
/Users/travis/.m2/repository/org/apache/hcatalog/hcatalog-pig-adapter/0.5.0-dev/hcatalog-pig-adapter-0.5.0-dev.jar
/Users/travis/.m2/repository/org/apache/hcatalog/hcatalog-pig-adapter/0.5.0-dev/hcatalog-pig-adapter-0.5.0-dev.jar.asc
/Users/travis/.m2/repository/org/apache/hcatalog/hcatalog-pig-adapter/0.5.0-dev/hcatalog-pig-adapter-0.5.0-dev.pom
/Users/travis/.m2/repository/org/apache/hcatalog/hcatalog-pig-adapter/0.5.0-dev/hcatalog-pig-adapter-0.5.0-dev.pom.asc
/Users/travis/.m2/repository/org/apache/hcatalog/hcatalog-pig-adapter/maven-metadata-local.xml
/Users/travis/.m2/repository/org/apache/hcatalog/hcatalog-server-extensions
/Users/travis/.m2/repository/org/apache/hcatalog/hcatalog-server-extensions/0.5.0-dev
/Users/travis/.m2/repository/org/apache/hcatalog/hcatalog-server-extensions/0.5.0-dev/hcatalog-server-extensions-0.5.0-dev.jar
/Users/travis/.m2/repository/org/apache/hcatalog/hcatalog-server-extensions/0.5.0-dev/hcatalog-server-extensions-0.5.0-dev.jar.asc
/Users/travis/.m2/repository/org/apache/hcatalog/hcatalog-server-extensions/0.5.0-dev/hcatalog-server-extensions-0.5.0-dev.pom
/Users/travis/.m2/repository/org/apache/hcatalog/hcatalog-server-extensions/0.5.0-dev/hcatalog-server-extensions-0.5.0-dev.pom.asc
/Users/travis/.m2/repository/org/apache/hcatalog/hcatalog-server-extensions/maven-metadata-local.xml
TW-MBP13-TCrawford:hcatalog travis$ 
{code}
                
> Add HCatalog to Maven Repository
> --------------------------------
>
>                 Key: HCATALOG-132
>                 URL: https://issues.apache.org/jira/browse/HCATALOG-132
>             Project: HCatalog
>          Issue Type: New Feature
>            Reporter: David Capwell
>            Assignee: Travis Crawford
>              Labels: maven
>
> HCat should be in maven main repositories

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to