[
https://issues.apache.org/jira/browse/HCATALOG-519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Travis Crawford updated HCATALOG-519:
-------------------------------------
Attachment: HCATALOG-519_pig_adapter_pom.1.patch
Reviewboard:
https://reviews.apache.org/r/7380/
Update the following subprojects to maven-ant-tasks for dependency resolution
(removing ivy):
* hcatalog-pig-adapter
* webhcat
* webhcat-java-client
Fix an issue with the top-level POM file where it contained a nested "project"
element (invalid syntax).
Improve the top-level "jar" target so it builds all jars in that target, rather
than scattering around different targets.
Remove either unused or duplicate property definitions. This is a major area
for improvement because it really introduces unnecessary confusion. Unused
property suggest certain values are configurable when in fact they are not, and
duplicate definitions confuse users attempting to understand what a value it
set to. This is an incremental step towards moving as many properties as is
reasonable to build.properties. When that has been achieved developers will
have a single place to see what parts of the build are configurable.
> Migrate pig-adapter/webhcat to maven dependencies and continue build cleanup
> ----------------------------------------------------------------------------
>
> Key: HCATALOG-519
> URL: https://issues.apache.org/jira/browse/HCATALOG-519
> Project: HCatalog
> Issue Type: Improvement
> Reporter: Travis Crawford
> Assignee: Travis Crawford
> Attachments: HCATALOG-519_pig_adapter_pom.1.patch
>
>
> Currently {{hcatalog-pig-adapter}} uses Ivy to manage its dependencies,
> specified in an {{ivy.xml}} file. When publishing to Maven we must generate a
> {{pom.xml}}.
> {{hcatalog-pig-adapter}} should use Maven for both resolving and publishing
> dependencies. We do this with some other subprojects and it works quite well,
> simplifying our build system.
--
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
