Mailing-List: contact notifications-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ant.apache.org
Date: Mon, 9 Jan 2012 04:15:40 +0000 (UTC)
From: "Sebastian Krueger (Issue Comment Edited) (JIRA)" <jira@apache.org>
To: notifications@ant.apache.org
Message-ID: 
 <1942970213.20650.1326082540857.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <508173517.6874.1325716300871.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Issue Comment Edited] (IVY-1330)
 samples/eclipse-plugin/ivy.xml does not work because of incorrect conf
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Sebastian Krueger edited comment on IVY-1330 at 1/9/12 4:13 AM:
----------------------------------------------------------------

patch is for rev 1051057
                
      was (Author: sebykrueger):
    patch if for rev 1051057
                  
> samples/eclipse-plugin/ivy.xml does not work because of incorrect conf
> ----------------------------------------------------------------------
>
>                 Key: IVY-1330
>                 URL: https://issues.apache.org/jira/browse/IVY-1330
>             Project: Ivy
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions: trunk
>            Reporter: Sebastian Krueger
>            Priority: Minor
>              Labels: documentation, patch
>         Attachments: patch.txt
>
>
> I have attached a patch to the ivy.xml that is used by the eclipse-plugin.html tutorial as this does not work.
> In the dependency section a reference to "linux" is made which does not exist. 
> The attached patch renames the gtk conf to linux.
> Also, the conf attribute in <ivy:cachepath/> does not point to anything that could ever work. So I have changed this to "linux" instead.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira