hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Allen Wittenauer (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HADOOP-5238) ivy publish and ivy integration does not cleanly work
Date Mon, 21 Jul 2014 19:58:40 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-5238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Allen Wittenauer resolved HADOOP-5238.
--------------------------------------

    Resolution: Fixed

> ivy publish and ivy integration does not cleanly work
> -----------------------------------------------------
>
>                 Key: HADOOP-5238
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5238
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 0.19.0
>            Reporter: Stefan Groschupf
>            Assignee: Giridharan Kesavan
>            Priority: Minor
>
> As far I understand the goal using ivy for hadoop is to be able intgrating hadoop easily
in thirdparty builds that uses transient dependency tools like ivy or maven. 
> The way ivy is currently integrated a couple hick ups. 
> + the generated artifact files have names that can't be used for maven or ivy. e.g. hadoop-version-core
but standard would be hadoop-core-version. This effects all those generated artifact files
like hadoop-version-example etc. This is caused by the use of ${final.name}-core.jar
> + This conflicts with the use of "${version}" in ivy.xml <info organisation="org.apache.hadoop"
module="${ant.project.name}" revision="${version}">. The result will be a error report
by ivy that found artifact and defined artifact name are different.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message