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

Rohini Palaniswamy commented on OOZIE-1218:
-------------------------------------------

The six new warnings are actually caused by addition of a the hcatalog-0.5 
hcataloglib pom. 

[WARNING] Some problems were encountered while building the effective model for 
org.apache.oozie:oozie-hcatalog:jar:0.5.0.oozie-4.1.0-SNA
  [WARNING] 'build.plugins.plugin.version' for 
com.atlassian.maven.plugins:maven-clover2-plugin is missing. @ 
org.apache.oozie:oozie-main:4
  [WARNING] 'build.plugins.plugin.version' for 
org.codehaus.mojo:findbugs-maven-plugin is missing. @ 
org.apache.oozie:oozie-main:4.1.0-SNAP
  [WARNING]
[WARNING] Could not transfer metadata asm:asm/maven-metadata.xml from/to 
local.repository (file:../../local.repository/trunk): No connect
  [WARNING] Could not transfer metadata asm:asm/maven-metadata.xml from/to 
local.repository (file:../../local.repository/trunk): No connect


bq. . -1 the patch seems to introduce 6 new javac warning(s)
 We are actually not checking for javac warnings but for maven warnings. This 
needs to be fixed. Opened JIRA OOZIE-1252 for that.
                
> Create a HCatalog Integration Guide
> -----------------------------------
>
>                 Key: OOZIE-1218
>                 URL: https://issues.apache.org/jira/browse/OOZIE-1218
>             Project: Oozie
>          Issue Type: Sub-task
>            Reporter: Rohini Palaniswamy
>            Assignee: Rohini Palaniswamy
>             Fix For: trunk
>
>         Attachments: OOZIE-1218-1.patch, OOZIE-1218-2.patch, 
> OOZIE-1218-3.patch, OOZIE-1218-3-trunk.patch
>
>
>   Need a twiki doc - HCatalog Integration Guide that explain systems 
> requiremenst (ie JMS, HCAT), oozie server configurations, the URI topic/JMS 
> mapping, oozie special configurations for it, hcat sharelib, etc.

--
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

Reply via email to