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

Konstantin Boudnik commented on BIGTOP-790:
-------------------------------------------

I can not build oozie 3.2.0 as a part of 0.3.1 release because of the following 
issue:
{noformat}
[INFO] Building Apache Oozie Share Lib Hive 3.2.0-incubating
[INFO] ------------------------------------------------------------------------
[WARNING] Could not transfer metadata asm:asm/maven-metadata.xml from/to 
local.repository (file:..
/../local.repository/trunk): No connector available to access repository 
local.repository (file:..
/../local.repository/trunk) of type legacy using the available factories 
WagonRepositoryConnectorF
actory
[WARNING] The POM for javax.jdo:jdo2-api:jar:2.3-ec is missing, no dependency 
information availabl
e
[WARNING] Failure to transfer asm:asm/maven-metadata.xml from 
file:../../local.repository/trunk wa
s cached in the local repository, resolution will not be reattempted until the 
update interval of 
local.repository has elapsed or updates are forced. Original error: Could not 
transfer metadata as
m:asm/maven-metadata.xml from/to local.repository 
(file:../../local.repository/trunk): No connector available to access 
repository local.repository (file:../../local.repository/trunk) of type legacy 
using the available factories WagonRepositoryConnectorFactory
{noformat}
                
> bump oozie version to 3.2.0
> ---------------------------
>
>                 Key: BIGTOP-790
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-790
>             Project: Bigtop
>          Issue Type: Sub-task
>          Components: General
>    Affects Versions: 0.3.1
>            Reporter: Anatoli Fomenko
>            Assignee: Anatoli Fomenko
>              Labels: 0.3.1
>             Fix For: 0.3.1
>
>         Attachments: BIGTOP-790.patch
>
>


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