[
https://issues.apache.org/jira/browse/HCATALOG-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13488861#comment-13488861
]
Travis Crawford commented on HCATALOG-543:
------------------------------------------
Yeah, let's get the poms published correctly.
Clearly all solutions here involve some level of tradeoff, which do you think
is least bad? There's this approach here, or I think we could duplicate the jar
versions in the top-level pom file (children will inherit those version
numbers). We'll have to put comments in both libraries.properties & pom.xml
about making changes in both places, but that's an easy to understand &
targeted change.
I'll take a look at whatever approach you'd like to take. Can you post a
reviewboard though? These build files are really hard to understand from just a
diff.
> Fix broken hcatalog poms
> ------------------------
>
> Key: HCATALOG-543
> URL: https://issues.apache.org/jira/browse/HCATALOG-543
> Project: HCatalog
> Issue Type: Bug
> Reporter: Francis Liu
> Assignee: Francis Liu
> Attachments: HCATALOG-543-1.patch, HCATALOG-543.patch,
> HCATALOG-543.patch
>
>
> All published poms except hcatalog-core are not working since the properties
> weren't resolved (ie ${hcatalog.version}).
> https://repository.apache.org/content/groups/snapshots/org/apache/hcatalog/webhcat-java-client/0.5.0-SNAPSHOT/webhcat-java-client-0.5.0-20121016.030800-8.pom
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
