From ivy-user-return-100-apmail-incubator-ivy-user-archive=incubator.apache.org@incubator.apache.org Wed Dec 06 15:16:49 2006 Return-Path: Delivered-To: apmail-incubator-ivy-user-archive@locus.apache.org Received: (qmail 82594 invoked from network); 6 Dec 2006 15:16:48 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 6 Dec 2006 15:16:48 -0000 Received: (qmail 49512 invoked by uid 500); 6 Dec 2006 15:16:56 -0000 Delivered-To: apmail-incubator-ivy-user-archive@incubator.apache.org Received: (qmail 49488 invoked by uid 500); 6 Dec 2006 15:16:56 -0000 Mailing-List: contact ivy-user-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ivy-user@incubator.apache.org Delivered-To: mailing list ivy-user@incubator.apache.org Received: (qmail 49479 invoked by uid 99); 6 Dec 2006 15:16:56 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Dec 2006 07:16:56 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: local policy) Received: from [204.246.4.173] (HELO paulsclub.isthmusgroup.net) (204.246.4.173) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Dec 2006 07:16:42 -0800 Received: by paulsclub.isthmusgroup.net (Postfix, from userid 1002) id 95239BA553; Wed, 6 Dec 2006 09:09:00 -0600 (CST) Received: from 204.246.8.179 (SquirrelMail authenticated user jbrugge) by mail.isthmusgroup.com with HTTP; Wed, 6 Dec 2006 09:09:00 -0600 (CST) Message-ID: <47224.204.246.8.179.1165417740.squirrel@mail.isthmusgroup.com> In-Reply-To: <635a05060612051516r4e5b6334wce08d552c946991@mail.gmail.com> References: <42768.204.246.8.179.1165351894.squirrel@mail.isthmusgroup.com> <635a05060612051516r4e5b6334wce08d552c946991@mail.gmail.com> Date: Wed, 6 Dec 2006 09:09:00 -0600 (CST) Subject: Re: Resolving latest "integration" artifacts From: "John Brugge" To: ivy-user@incubator.apache.org User-Agent: SquirrelMail/1.4.2 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 Importance: Normal X-Virus-Checked: Checked by ClamAV on apache.org Okay, I've made some progress, and have most of it working, but still have a couple of questions. It appears that the first big missing piece was that the ivy file for the component was not actually being uploaded, and so, as Gilles guessed, the ivy file I was getting on resolve was a default one. I think my confusion over this is something that could be entered as a defect; the Ant task wasn't reporting a failure in the ssh resolver, so I too quickly assumed that everything was okay. ivy-publish: [ivy:publish] :: publishing :: [ inat3 | ldap-impl-jndi ] [ivy:publish] published ldap-impl-jndi to http://cvs.svc.tds.net/inat3deps/inat3deps/inat3/ldap-impl-jndi-1.0.0-dev-1.0.0-dev.jar [ivy:publish] published ivy to http://cvs.svc.tds.net/inat3deps/inat3deps/ivy/ldap-impl-jndi/ivy-ivy.xml When I checked the files on the server I saw the upload never really happened. I ran 'ant resolve -d' and saw the problem quickly: [ivy:publish] SShRepository:put called: http://cvs.svc.tds.net/inat3deps/inat3deps/ivy/ldap-impl-jndi/ivy-ivy.xml.md5 [ivy:publish] ERROR: Wrong scheme in URI. Expected ssh as scheme!: http://cvs.svc.tds.net/inat3deps/inat3deps/ivy/ldap-impl-jndi/ivy-ivy.xml.md5 [ivy:publish] ERROR: The uri is in the wrong format. [ivy:publish] ERROR: Please use scheme://user:pass@hostname/path/to/repository Once I fixed my mixed up ant properties, I got the publishing working and the ivy file went up fine along with the component. When I went to resolve from a project that depends on it, it worked like a charm. Success! The last piece of the puzzle was to get it to re-publish the ivy file when the JAR file changed. What I found was that if I changed the JAR file and ran the publish task again, the timestamps of the files on the server changed (both the JAR and the ivy file), but the contents didn't. I finally added 'forcedeliver="true"' to the publish task and it is now working the way I think it should. So now my question is this: for integration artifacts, do I need to have "forcedeliver='true'" in order to get my changing JAR files published properly? I'm not clear on the 'deliver' concept, I realize, and now I can't find it in the docs again (I did find it once). Thanks again, John Xavier Hanin said: > Mmm, it's strange, what you did first should be working. Using the > changingPattern should tell ivy that your -dev revision is a changing one, > and Ivy should check for updates of your jars. So it may be a bug in > Ivy... > > On 12/5/06, John Brugge wrote: >> >> I am trying to get Ivy to recognize updated "integration" releases of >> JAR >> files in our repository, and am not having much luck. I am new to Ivy, >> so >> I may well be missing some core concept or misusing some features. Any >> tips are appreciated. >>