[
https://issues.apache.org/jira/browse/HCATALOG-132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13411742#comment-13411742
]
Travis Crawford commented on HCATALOG-132:
------------------------------------------
Quick update:
I just published what I currently have to a branch in case anyone wants to give
some early feedback, since it sounds like there's some urgency around this.
https://github.com/traviscrawford/hcatalog/compare/HCATALOG-132_publish_to_maven_2
The main issue we have is generating the pom files correctly. We generate three
jars from one ivy.xml file:
* hcatalog.jar
* hcatalog-core.jar
* hcatalog-server-extensions.jar
Which causes issues when generating pom files because only the top jar in that
list actually has an ivy.xml file (per the org & module are defined in
ivy.xml). hcatalog-pig-adapter is fine because it has its own ivy.xml, and its
pom is generated correctly.
I think we want to move hcatalog-server-extensions into a subproject like the
pig adapter, so it has its own ivy.xml. Then for hcatalog/hcatalog-core we
simply fudge the pom file until we stop publishing hcatalog.jar.
Thoughts? If this sounds good I'll start down this path.
> 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
