Return-Path: 
 <ivy-user-return-8120-apmail-ant-ivy-user-archive=ant.apache.org@ant.apache.org>
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 74909970E
	for <apmail-ant-ivy-user-archive@www.apache.org>;
 Fri, 23 Sep 2011 13:05:13 +0000 (UTC)
Received: (qmail 68810 invoked by uid 500); 23 Sep 2011 13:05:13 -0000
Delivered-To: apmail-ant-ivy-user-archive@ant.apache.org
Received: (qmail 68749 invoked by uid 500); 23 Sep 2011 13:05:12 -0000
Mailing-List: contact ivy-user-help@ant.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:ivy-user-help@ant.apache.org>
List-Unsubscribe: <mailto:ivy-user-unsubscribe@ant.apache.org>
List-Post: <mailto:ivy-user@ant.apache.org>
List-Id: <ivy-user.ant.apache.org>
Reply-To: ivy-user@ant.apache.org
Delivered-To: mailing list ivy-user@ant.apache.org
Received: (qmail 68737 invoked by uid 99); 23 Sep 2011 13:05:12 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 23 Sep 2011 13:05:12 +0000
X-ASF-Spam-Status: No, hits=1.5 required=5.0
	tests=FREEMAIL_FROM,HTML_MESSAGE,NORMAL_HTTP_TO_IP,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL,WEIRD_PORT
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of david.dhcinc@gmail.com
 designates 209.85.210.173 as permitted sender)
Received: from [209.85.210.173] (HELO mail-iy0-f173.google.com)
 (209.85.210.173)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 23 Sep 2011 13:05:06 +0000
Received: by iagf6 with SMTP id f6so4718902iag.4
        for <ivy-user@ant.apache.org>; Fri, 23 Sep 2011 06:04:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        bh=LErDtkxGN09eLe9CZebzCXfeoPr3amo5y6mA/y2XTLQ=;
        b=T0pfD4euSxqWOfsX7vzfodJ65Nhtvi1fpopB0woIFY4c5eSoHiztLUswqm10bicErV
         LofAbboXfNVCVboNKY4TXSMKgViAaKWg9OSsDcPrApZzY0erkeE8k7BKd1RUQncOet6k
         DJfl8tpLR2BXEOB3Ppz75VCnCVbHWHIfLk81c=
MIME-Version: 1.0
Received: by 10.43.130.134 with SMTP id hm6mr1254193icc.50.1316783085440; Fri,
 23 Sep 2011 06:04:45 -0700 (PDT)
Received: by 10.231.108.133 with HTTP; Fri, 23 Sep 2011 06:04:45 -0700 (PDT)
In-Reply-To: 
 <CAOYQz5iZ6MEHPptRpWOXxDkJYy4_1JCB1cVq26=AzoTmcp9G4A@mail.gmail.com>
References: 
 <CAHVrPb9FYcLNHFxgbEbewWckivBckBSSZtFQAR1RBSiDz8crHw@mail.gmail.com>
	<CAOYQz5iZ6MEHPptRpWOXxDkJYy4_1JCB1cVq26=AzoTmcp9G4A@mail.gmail.com>
Date: Fri, 23 Sep 2011 09:04:45 -0400
Message-ID: 
 <CAHVrPb9nzJwvSTHsxWbLbTD8BTOqphf5R3GM6Z4-NBtiykvb9w@mail.gmail.com>
Subject: Re: Publishing POM to Artifactory not working
From: David Haynes <david.dhcinc@gmail.com>
To: ivy-user@ant.apache.org
Content-Type: multipart/alternative; boundary=20cf307d01d00dced304ad9b7465

--20cf307d01d00dced304ad9b7465
Content-Type: text/plain; charset=ISO-8859-1

Thanks. That was the issue. On to the next problem!

On Thu, Sep 22, 2011 at 5:03 PM, Rod MacKenzie <rod.n.mackenzie@gmail.com>wrote:

> Do you have an entry in the publications section of the ivy file for
> the pom file?
>
> Here's the publications section from an ivy file I've been using to
> publish to a Nexus repository
> <publications>
>        <artifact type="jar" ext="jar"/>
>        <artifact type="source" ext="jar" m:classifier="sources"/>
>        <artifact type="javadoc" ext="jar" m:classifier="javadoc"/>
>        <artifact type="descriptor" ext="pom"/>
> </publications>
>
> I think the artifacts pattern in the publish task is used only to find
> the artifacts and isn't used to determine what to publish. Hope this
> helps.
>
> Rod
>
> On 22 September 2011 18:27, David Haynes <david.dhcinc@gmail.com> wrote:
> > Hey there.
> > I am having a bit of a problem publishing a pom file to my Artifactory
> > repository using the Ant tools.
> > The ant target does not seem to be finding the pom file to publish.
> >
> > Here is a piece from the build.xml file:
> >        <ivy:makepom ivyfile="ivy.xml"
> > pomfile="${dist.dir}/${name}-${version}.pom" conf="default, runtime">
> >            <mapping conf="default" scope="compile"/>
> >            <mapping conf="runtime" scope="runtime"/>
> >        </ivy:makepom>
> >
> >        <ivy:publish organisation="${org}" module="${name}"
> > revision="${version}-SNAPSHOT"
> >            resolver="libs-snapshot-local" srcivypattern="ivy.xml"
> > update="true" overwrite="true" publishivy="false">
> >            <artifacts pattern="${dist.dir}/[artifact]-${version}.[ext]"/>
> >            <artifacts pattern="${dist.dir}/[artifact]-${version}.pom"/>
> >        </ivy:publish>
> >
> > My resolver looks like this:
> > <url name="libs-snapshot-local" m2compatible="true">
> >     <artifact pattern="
> >
> http://192.168.215.245:8081/artifactory/libs-snapshot-local/[organisation]/[module]/[revision]/[artifact]-[revision].[ext]
> "
> > /
> >      <ivy pattern="
> >
> http://192.168.215.245:8081/artifactory/libs-snapshot-local/[organisation]/[module]/[revision]/ivy-[revision].xml
> "
> > />
> >  </url>
> >
> > When I run the build, I get the following:
> > [ivy:publish] :: publishing :: com.cinbell.cbts#rest-lib
> > [ivy:publish]   published rest-lib to
> >
> http://192.168.215.245:8081/artifactory/libs-snapshot-local/com/cinbell/cbts/rest-lib/1.0.0-SNAPSHOT/rest-lib-1.0.0-SNAPSHOT.jar
> >
> > And that is what shows up in the Artifactory repository.
> >
> > Notice that there is no attempt to publish the pom file....
> >
> > The pom file is generated and is in the ${dist.dir} directory as
> > [artifact]-${version}.pom.
> >
> > I am using ivy version 2.2.0.
> >
> > If anyone has any suggestions, I would love to hear them. I am out of
> ideas
> > on this one.
> >
> > Thanks
> > -david-
> >
>

--20cf307d01d00dced304ad9b7465--