[jira] Resolved: (IVY-1212) artifactreport ant task doesn't honor log attribute

["Maarten Coene (JIRA)" <ji...@apache.org>]

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

Maarten Coene resolved IVY-1212.
--------------------------------

         Assignee: Maarten Coene
    Fix Version/s: 2.2.0
       Resolution: Fixed

Fixed in both trunk and 2.2.x branch.
Could you give it a try to see if there are no other messages logged somewhere?

> artifactreport ant task doesn't honor log attribute
> ---------------------------------------------------
>
>                 Key: IVY-1212
>                 URL: https://issues.apache.org/jira/browse/IVY-1212
>             Project: Ivy
>          Issue Type: Bug
>          Components: Ant
>    Affects Versions: 2.1.0
>            Reporter: Phil Clay
>            Assignee: Maarten Coene
>            Priority: Minor
>             Fix For: 2.2.0
>
>
> The artifactreport doesn't honor the log attribute.  I set log="quiet" because I don't want to see all the...
> [ivy:artifactreport] 	found xxx in yyy
> ...messages in my ant output.  However, the messages still appear.
> The problem seems to be that the log field is not set on the ResolveOptions created in the IvyArtifactReport task...
> {code}
>             IvyNode[] dependencies = getIvyInstance().getResolveEngine().getDependencies(
>                 md,
>                 new ResolveOptions().setConfs(confs).setResolveId(
>                     getResolveId()).setValidate(doValidate(getSettings())), null);
> {code}
> I think the above code should instead be (notice the new setLog call)...
> {code}
>             IvyNode[] dependencies = getIvyInstance().getResolveEngine().getDependencies(
>                 md,
>                 new ResolveOptions()
>                     .setConfs(confs)
>                     .setLog(getLog())
>                     .setResolveId(getResolveId())
>                     .setValidate(doValidate(getSettings())),
>                 null);
> {code}
> I'm guessing the RetrieveOptions created a few lines lower need the same setLog call added as well.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.