[
https://issues.apache.org/jira/browse/HCATALOG-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13488831#comment-13488831
]
Travis Crawford commented on HCATALOG-543:
------------------------------------------
Hey [~toffer], good catch. This is happening because of the
{{properties-maven-plugin}} maven plugin, which makes a properties file
available in your {{pom.xml}}. I chose to use this plugin so we could easily
keep the ivy/maven dependencies on the same versions.
Ideally we could move everything to {{pom.xml}} files for dependencies, and no
longer have {{libraries.properties}}, putting versions in the hcatalog parent
pom.
An issue here is reorganizing {{core}} into a proper submodule. I'd prefer to
do that instead of continuously having to work around this issue. If that
sounds good I can take a look at it.
> 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
