Return-Path: X-Original-To: apmail-ant-ivy-user-archive@www.apache.org Delivered-To: apmail-ant-ivy-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D482944A9 for ; Thu, 19 May 2011 15:59:29 +0000 (UTC) Received: (qmail 30848 invoked by uid 500); 19 May 2011 15:59:29 -0000 Delivered-To: apmail-ant-ivy-user-archive@ant.apache.org Received: (qmail 30817 invoked by uid 500); 19 May 2011 15:59:29 -0000 Mailing-List: contact ivy-user-help@ant.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ivy-user@ant.apache.org Delivered-To: mailing list ivy-user@ant.apache.org Received: (qmail 30809 invoked by uid 99); 19 May 2011 15:59:29 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 May 2011 15:59:29 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of notzippy@gmail.com designates 74.125.82.173 as permitted sender) Received: from [74.125.82.173] (HELO mail-wy0-f173.google.com) (74.125.82.173) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 May 2011 15:59:24 +0000 Received: by wyb42 with SMTP id 42so2368355wyb.4 for ; Thu, 19 May 2011 08:59:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:from:date:message-id:subject:to :content-type; bh=Su/xEqIRjKH+jcplZYXRGyKghUKo/6mLrWKWtc3rcmY=; b=PmJJyFvVrKTaH7Oea8m7yH1M3WZfAZ0dXaOoRjDeyYXYKkqFUnuCJguPJbK61n68Mu wO1FLlL81JT5FaeKN50bYUPEyb70I2SAGRZVaKzdS+5YKPtp0TAGW/dT+O3bwmFvytrA BVbTXGEwjskkAJw+udK0513T3mfBGqtDGFf1M= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type; b=PTa58n6GupOSboTNaRPQw9pKnr9THNqRyVWsrhwdH8BenasKoIcfKVSqlvjFOcS0zX 5Cni21XEWASITTQuzROTdd9tk/K6Oeum4yXGFQuCpukMaN7hvCW49D7/xqKuNvGalnYE Xy7zpIBAdZ8DN742E3HAy60VueNMtxgmdRsMg= Received: by 10.216.221.22 with SMTP id q22mr3259244wep.37.1305820743091; Thu, 19 May 2011 08:59:03 -0700 (PDT) MIME-Version: 1.0 Received: by 10.216.90.197 with HTTP; Thu, 19 May 2011 08:58:43 -0700 (PDT) From: Not Zippy Date: Thu, 19 May 2011 10:58:43 -0500 Message-ID: Subject: Ivy publish and retrieval questions To: ivy-user@ant.apache.org Content-Type: multipart/alternative; boundary=0016e65b5b688846b604a3a315a8 --0016e65b5b688846b604a3a315a8 Content-Type: text/plain; charset=ISO-8859-1 Hi I am trying to create a project which publishes the jar and source code to my archiva server (using ant script). This part is easy and it publishes the jars and files like: foo-1.0.jar foo-source-1.0.jar Item 1) Now I want to reference that published project in another project in eclipse. But eclipse will only recognize the source code if it is the suffix of the artifact. The only way I have found to fix this is to specify a pattern for the publishing resolver like pattern="[organisation]/[module]/[revision]/[artifact].[ext]" so the published files look like foo.jar foo-source.jar Isn't that a bit more difficult then it should be ? Shouldn't eclipse be able to be configured to determine a source file by some other means then just the suffix of the file name ? Item 2) Now I want to retrieve a particular configuration from the server BUT the ibiblio resolver ignores ivy.xml files so I am forced to use a dual resolver like Once again is that not more difficult then it needs to be ? If the ibiblio resolver retrieved the ivy file this would simplify things greatly. Just some thoughts.. NZ --0016e65b5b688846b604a3a315a8--