hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Giridharan Kesavan (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-5238) ivy publish and ivy integration does not cleanly work
Date Wed, 16 Sep 2009 18:53:57 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-5238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12756173#action_12756173
] 

Giridharan Kesavan commented on HADOOP-5238:
--------------------------------------------

HADOOP-5107 would solve this issue as well.

> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message