From ivy-user-return-984-apmail-incubator-ivy-user-archive=incubator.apache.org@incubator.apache.org Wed Jun 13 14:23:13 2007 Return-Path: Delivered-To: apmail-incubator-ivy-user-archive@locus.apache.org Received: (qmail 58559 invoked from network); 13 Jun 2007 14:23:13 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 13 Jun 2007 14:23:13 -0000 Received: (qmail 4974 invoked by uid 500); 13 Jun 2007 14:23:16 -0000 Delivered-To: apmail-incubator-ivy-user-archive@incubator.apache.org Received: (qmail 4853 invoked by uid 500); 13 Jun 2007 14:23:16 -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 4844 invoked by uid 99); 13 Jun 2007 14:23:16 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Jun 2007 07:23:16 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of frank.kemmer@gmail.com designates 64.233.166.182 as permitted sender) Received: from [64.233.166.182] (HELO py-out-1112.google.com) (64.233.166.182) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Jun 2007 07:23:12 -0700 Received: by py-out-1112.google.com with SMTP id p76so569552pyb for ; Wed, 13 Jun 2007 07:22:51 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=AW5OvgJ4mia0e9yUJuYN0+8B7JJdZRywEFhcy3r1L8jC7kpV99dBfaXqlsV9PJTVezRIfxpxyH17Uvl03NVRw2n5hkYcF/s89SNmRWM8CV7AQfTDtsFdGApzfM2ubKoFtxpF2tBirCKjKv0ue4to63ZnjRQW1J1oUn6T34Lk48U= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=etv0/C2qPWXn3tLvnjqBwoWViW5qsb3tV4bAOgw2PuGLD96PSDCPJMFI2dvH1twzWQTgUGXJYAe/QTvjQX9tphB6OW6422mXRI9QDp+7OPBUlIvo0oigXj6rmebYouruG0RBEQbtLTbpkadFsX840/QFPXMw2B3e/pwWlVlR1wg= Received: by 10.65.73.16 with SMTP id a16mr1158384qbl.1181744571483; Wed, 13 Jun 2007 07:22:51 -0700 (PDT) Received: by 10.65.185.5 with HTTP; Wed, 13 Jun 2007 07:22:51 -0700 (PDT) Message-ID: <85531cb40706130722s2fa42321n354354b20723f3d1@mail.gmail.com> Date: Wed, 13 Jun 2007 16:22:51 +0200 From: "Frank Kemmer" To: ivy-user@incubator.apache.org Subject: Re: How-to build an enterprise repository with source-attachments ... In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <85531cb40706040351o71db7cb0l7d29751b03ccb6e0@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org > > Another problem I experienced: Some projects have Source Attachments > > defined in Maven2 for their binary distribution jar. I think, the > > source artifact description can be found in the Maven POM. How can I > > /convince/ Ivy to use this information, to add the source artifacts to > > the given Ivy module at hand? > > I thought the -src.jar were not present in the pom.xml. I thought > that the link between the two could only be deduced from the layout. > Did you have an example of src declared in the pom? You are right. No info in the POM. It's just by convention of the artifact name in the same directory. But the ibiblio resolver could use this layout to generate a corresponding ivy file ... but doesn't ... :) Currently I think, that it is best, to setup the enterprise repository by hand. Downloading every JAR by hand and writing a mini project to publish it into the enterprise repository. This is a little bit frustrating but seems to be the most stable & safe approach. Currently we are working on a project to generate ivy.xml files by analyzing the real JAR dependencies (we use the jaranalyzer). For the next enterprise repo I will use that approach ... :)