Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id C44A0200BB1 for ; Thu, 3 Nov 2016 18:51:41 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id C2CA1160AFF; Thu, 3 Nov 2016 17:51:41 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id E0828160AE5 for ; Thu, 3 Nov 2016 18:51:40 +0100 (CET) Received: (qmail 6188 invoked by uid 500); 3 Nov 2016 17:51:40 -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 6174 invoked by uid 99); 3 Nov 2016 17:51:39 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Nov 2016 17:51:39 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 2BE8D18030C for ; Thu, 3 Nov 2016 17:51:39 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.381 X-Spam-Level: ** X-Spam-Status: No, score=2.381 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, WEIRD_PORT=0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id eFh95qrw6mLT for ; Thu, 3 Nov 2016 17:51:37 +0000 (UTC) Received: from mail-oi0-f53.google.com (mail-oi0-f53.google.com [209.85.218.53]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 9B97C5F24F for ; Thu, 3 Nov 2016 17:51:36 +0000 (UTC) Received: by mail-oi0-f53.google.com with SMTP id v84so100722681oie.3 for ; Thu, 03 Nov 2016 10:51:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=9mZigGqNQcyb4e6SuTjbNKUmwDRxmy1c0oGmBI8irvg=; b=LZLUQs1WsKvBCLl0FqJQteFD7DqYhKN7dRQosc/asnQ1VEJ9lzxPwHmgW0tJuM6BaJ 6Y5quHWyW4xIHrWjz/3yo0L26KU7qHGk4tbBBPrYf9UcJBN290g0/F80CSLxPfsL8X6X bBtYCBYFBJlM+Cv2+2LB0pDHnLqTf1EjllAnGHinkItU3FA0kmmWwpbe4hZMLA+IZ0jd rWqe0oVnyT/xsWGFWZR+pc7TsO2W1yExhrk3UNbqGiAjL+ANfbYrMWo9Wsa/VzzHCXXC oMcqVFeAxVQ0Tj0x/0ijUX5y676FmHaJu19CXX3twW7swbUXf1SQyqTeeMJTKCfbTzYs nBJA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=9mZigGqNQcyb4e6SuTjbNKUmwDRxmy1c0oGmBI8irvg=; b=EJ5RkqaSC4O4ZcxNqysMjgCY+Ub9OPJuiOEwIddJxxwvgUfk4Wt6W7QqTjj9rXz+cG OofCdeByXYlsOFMIO2m3DG/eeWEvOiyrwXxooSBEtt0c7CvCydOTPH/+8KTby03YKS9h diEqC9uUpzrN23rQ5qR+QDHsrLsqdbybbCyE2zDF96AOIh9RDIhP+FrQk7pkIQWzu41a lV2NASj7IMAtOUmuWBntHYR1f+2d5i6YPy07hyNZwEXAYCsDGx2JyzonqTZaPcfEW0Dj PA6lhXtMe6Y5ZWwGfrfNBCbj+JqjvwAsq4CE+MLMMzeNYfvZqQq/D2tT4PItdUCTW+N6 dBHw== X-Gm-Message-State: ABUngvfkPTaeqHUI+ioDe1T+sjdS0j0HkXTvbhEr0WQ6QmOEEt5MuqMIAjkdSoaOoWaiopmQnHLl2QT0vBXT0w== X-Received: by 10.157.8.52 with SMTP id 49mr7608523oty.153.1478195491805; Thu, 03 Nov 2016 10:51:31 -0700 (PDT) MIME-Version: 1.0 Received: by 10.157.29.249 with HTTP; Thu, 3 Nov 2016 10:51:31 -0700 (PDT) In-Reply-To: <19157c605d3041d7b13a9f674a91592b@SDREXC3.salt-solutions.de> References: <19157c605d3041d7b13a9f674a91592b@SDREXC3.salt-solutions.de> From: Vincent Case Date: Thu, 3 Nov 2016 13:51:31 -0400 Message-ID: Subject: Re: Issue Publishing with UrlResolver and later Resolving with IBiblioResolver To: ivy-user@ant.apache.org Content-Type: multipart/alternative; boundary=94eb2c04844e32a1aa054069352b archived-at: Thu, 03 Nov 2016 17:51:42 -0000 --94eb2c04844e32a1aa054069352b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Thank you for your very clear explanation. I will use the url resolver for both publishing the resolving. -Vincent On Wed, Nov 2, 2016 at 2:10 PM, Gei=C3=9Fler, Daniel < daniel.geissler@salt-solutions.de> wrote: > The ibiblio resolver is for dependency resolution in maven repositories. > If you don't publish a pom.xml then resolving might be somewhat strange. > > So you'll need to create a pom first: http://ant.apache.org/ivy/ > history/2.4.0/use/makepom.html where you can map your ivy configurations > to maven scopes. > Add the pom to your publish section in the ivy.xml and try it again. > > When resolving with the ibiblio resolver you are however bound to > automatically created configurations that meet the maven scopes (master, > compile, test ...). As far as I remember default is a combination of mast= er > (the artifact itself) and runtime (it's runtime dependencies). > > When publishing with ivy.xml the url resolver should be sufficient and > even faster than ibiblio. > > Hope that helps. > > Kind regards > Daniel > > _____________________________________ > > www.salt-solutions.de > > Gesch=C3=A4ftsf=C3=BChrer: Dr. Bernhard Bl=C3=BCthner, Norbert H. Fiedler= , Dieter Heyde, > Markus Honold > Sitz: M=C3=BCnchen, AG M=C3=BCnchen, HRB 146081 > > -----Urspr=C3=BCngliche Nachricht----- > Von: Vincent Case [mailto:vincent.case@gmail.com] > Gesendet: Mi, 2. November 2016 18:36 > An: ivy-user@ant.apache.org > Betreff: Issue Publishing with UrlResolver and later Resolving with > IBiblioResolver > > Problem Overview: My goal is to publish an artifact using the UrlResolver > and then retrieve it using the IBiblioResolver. However, resolve fails i= f > the dependency conf mapping is to something other than "->default". Wha= t > I observe is: > 1- The ivy:resollve task succeeds if the UrlResolver is used for resolvin= g > as well as publishing. > 2- The ivy:resolve task succeeds with the IBiblioResolver only if the con= f > mapping is to the "->default" for the published artifact. > 3- When the dependency conf mapping is to something other than ->default, > verbose logging indicates that "no ivy file file found for XXX: using > default data" > 4- When the "m2compitiblity" settings are the same for publish and > resolve, the failure is always the same, regardless of its setting, and > regardless of the "usepoms" setting. > > I have created a trivial example (below) that exhibits the behavior > described above. > > Thanks for your help. > > =3D=3D=3D settings.properties =3D=3D=3D > pattern.artifacts.pub=3D[organization]/[module]/[ > revision]/[type]s/[artifact].[ext] > pattern.ivy.pub=3D[organization]/[module]/[revision]/[type]s/[ > artifact].[ext] > > =3D=3D=3D settings.xml =3D=3D=3D > > defaultResolver=3D"resolver-res" /> > > > pattern=3D"${artifactory.url}/${rps.repo.integration}/${ > pattern.artifacts.pub}" > /> > pattern.ivy.pub}" > /> > > root=3D"${artifactory.url}/${rps.repo.integration}" > pattern=3D"${pattern.artifacts.pub}" > /> > > > > > =3D=3D=3D ivy.xml for Publish =3D=3D=3D > > > > > extends=3D"compile"/> > > > > > > > =3D=3D=3D ivy.xml for Resolving the published artifact =3D=3D=3D version=3D"2.0"> > > > extends=3D"compile"/> > > > transitive=3D"false" conf=3D"compile->runtime" /> > > =3D=3D=3D Build File =3D=3D=3D > xmlns:ivy=3D"antlib:org.apache.ivy.ant" > > > > > > value=3D"c:/dev/apache-ivy-2.4.0/build/artifact/jars/ivy.jar" /> classpath=3D"${IvyJarFile}" > resource=3D"org/apache/ivy/ant/antlib.xml" > uri=3D"antlib:org.apache.ivy.ant" > /> > > > > > > >file:pub.jar {pattern.artifacts.built}" > resolver=3D"resolver-pub" > pubrevision=3D"1.0" > forcedeliver=3D"true" > status=3D"integration" > overwrite=3D"true" > conf=3D"compile,runtime" > /> > > > > > > > > > /> includeemptydirs=3D"true" /> > includeemptydirs=3D"true" /> > > > > > > =3D=3D=3D Verbose Logging Output =3D=3D=3D=3D > > [ivy:resolve] tried http://centos-7:8882/ > artifactory/rps-integration/com/vcase/rps/pub/[revision]/jars/pub.jar > [ivy:resolve] resolver-res: no ivy file found for > com.vcase.rps#pub;latest.integration: using default data > [ivy:resolve] [1.0] com.vcase.rps#pub > : > : > [ivy:resolve] :: com.vcase.rps#pub;1.0: configuration not found > in com.vcase.rps#pub;1.0: 'runtime'. It was required from > com.vcase.rps#;working@vcase-PC-new compile > > > EOM > --94eb2c04844e32a1aa054069352b--