avro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Doug Cutting (JIRA)" <j...@apache.org>
Subject [jira] Updated: (AVRO-122) ivy task does not enjoy being defined twice (build error)
Date Thu, 24 Sep 2009 21:48:16 GMT

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

Doug Cutting updated AVRO-122:
------------------------------

       Resolution: Fixed
    Fix Version/s: 1.2.0
           Status: Resolved  (was: Patch Available)

I just committed this.  Thanks, Pat!

> ivy task does not enjoy being defined twice (build error)
> ---------------------------------------------------------
>
>                 Key: AVRO-122
>                 URL: https://issues.apache.org/jira/browse/AVRO-122
>             Project: Avro
>          Issue Type: Bug
>          Components: java
>    Affects Versions: 1.1.0
>            Reporter: Patrick Hunt
>            Assignee: Patrick Hunt
>            Priority: Minor
>             Fix For: 1.2.0
>
>         Attachments: AVRO-122.patch
>
>
> This same issue exists in ZOOKEEPER-535
> ---------------
> Ant resolves the same dependencies multiple times if multiple targets are run on the
command line:
> "ant b c", where b and c both depend on a, results in a being executed twice. However
if you have a
> target d which depends on both b and c, "ant d" will only result in a being executed
once.
> say "ant compile-java compile-java-test" is run, this will currently fail as ivy-init
is run twice, resulting in the taskdef failing.
> Rather we need a guard on the ivy-init target itself to ensure it isn't run twice.
> ie: put an unless attrib on ivy-init, then set that property in the body of the target

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