Return-Path: 
 <ivy-user-return-7335-apmail-ant-ivy-user-archive=ant.apache.org@ant.apache.org>
Delivered-To: apmail-ant-ivy-user-archive@www.apache.org
Received: (qmail 69005 invoked from network); 18 Oct 2010 16:54:19 -0000
Received: from unknown (HELO mail.apache.org) (140.211.11.3)
  by 140.211.11.9 with SMTP; 18 Oct 2010 16:54:19 -0000
Received: (qmail 12643 invoked by uid 500); 18 Oct 2010 16:54:19 -0000
Delivered-To: apmail-ant-ivy-user-archive@ant.apache.org
Received: (qmail 12580 invoked by uid 500); 18 Oct 2010 16:54:18 -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 12572 invoked by uid 99); 18 Oct 2010 16:54:17 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 18 Oct 2010 16:54:17 +0000
X-ASF-Spam-Status: No, hits=-2.3 required=10.0
	tests=RCVD_IN_DNSWL_MED,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: local policy)
Received: from [15.192.0.45] (HELO g5t0008.atlanta.hp.com) (15.192.0.45)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 18 Oct 2010 16:54:09 +0000
Received: from G1W0400.americas.hpqcorp.net (g1w0400.americas.hpqcorp.net
 [16.236.31.10])
	(using TLSv1 with cipher RC4-MD5 (128/128 bits))
	(No client certificate requested)
	by g5t0008.atlanta.hp.com (Postfix) with ESMTPS id 969372439B
	for <ivy-user@ant.apache.org>; Mon, 18 Oct 2010 16:53:47 +0000 (UTC)
Received: from G5W0325.americas.hpqcorp.net (16.228.8.67) by
 G1W0400.americas.hpqcorp.net (16.236.31.10) with Microsoft SMTP Server (TLS)
 id 8.2.176.0; Mon, 18 Oct 2010 16:52:41 +0000
Received: from GVW1115EXC.americas.hpqcorp.net ([16.228.11.77]) by
 G5W0325.americas.hpqcorp.net ([16.228.8.67]) with mapi; Mon, 18 Oct 2010
 16:52:41 +0000
From: "Bailey, Darragh" <dbailey@hp.com>
To: "ivy-user@ant.apache.org" <ivy-user@ant.apache.org>
Date: Mon, 18 Oct 2010 16:52:39 +0000
Subject: Problem getting a publish to local filesystem working
Thread-Topic: Problem getting a publish to local filesystem working
Thread-Index: Actu5N+ByZ2uNQTcRFmfLkyyuyKZKA==
Message-ID: 
 <FF452E17060D614D89BF7FD3A07A8833560126AC63@GVW1115EXC.americas.hpqcorp.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Virus-Checked: Checked by ClamAV on apache.org


I'm running into a problem with performing a local publish:

Currently using Ivy 2.2.x-local-20100609212354

Resolver used for local publishing.
    <filesystem name=3D"local" local=3D"true">
      <ivy pattern=3D"${dest.repo.dir}/[organisation]/[module]/[revision]/i=
vy-[revision].xml" />
      <artifact pattern=3D"${dest.repo.dir}/[organisation]/[module]/[revisi=
on]/[type]s/[artifact]-[revision].[ext]" />
      <!-- <artifact pattern=3D"${dest.repo.dir}/[organisation]/[module]/[r=
evision]/[type]s/[artifact].[ext]" /> -->
    </filesystem>


This works:
    <ivy:publish artifactspattern=3D"${dist.dir}/[artifact]-[revision].[ext=
]"
      conf=3D"*(public)"
      pubrevision=3D"${project.version.main}"
      resolver=3D"local"
      status=3D"integration"
      forcedeliver=3D"true"
      />

:: delivering :: org.my#my-module#trunk;working@my-build-machine :: 1.0.1 :=
: integration :: Mon Oct 18 17:14:11 IST 2010
        delivering ivy file to /build/user/me/my/module/dir/trunk/dist/ivy-=
1.0.1.xml
:: publishing :: org.my#my-module
        published my-module to /home/me/.ivyrepo/org.my/my-module/1.0.1.par=
t/jars/my-module-1.0.1.jar
        published ivy to /home/me/.ivyrepo/org.my/my-module/1.0.1.part/ivy-=
1.0.1.xml
        publish commited: moved /home/me/.ivyrepo/org.my/my-module/1.0.1.pa=
rt
                to /home/me/.ivyrepo/org.my/my-module/1.0.1

This doesn't:
    <ivy:publish artifactspattern=3D"${dist.dir}/[artifact]-[revision].[ext=
]"
      conf=3D"*(public)"
      revision=3D"${project.version.main}"
      pubrevision=3D"${project.version.full}"
      resolver=3D"local"
      status=3D"integration"
      forcedeliver=3D"true"
      />

BUILD FAILED
[ivy:publish] :: delivering :: org.my#my-module#trunk;1.0.1 :: 1.0.1-1 :: i=
ntegration :: Mon Oct 18 17:48:14 IST 2010

/build/user/me/my/module/dir/trunk/build.xml:162: org.my#my-module#trunk;1.=
0.1: java.lang.IllegalStateException: ivy file not found in cache for org.m=
y#my-module#trunk;1.0.1: please resolve dependencies before delivering (/ho=
me/me/.ivy2/cache/resolved-org.my-my-module-1.0.1.xml)
        at org.apache.ivy.core.deliver.DeliverEngine.deliver(DeliverEngine.=
java:112)
        at org.apache.ivy.Ivy.deliver(Ivy.java:586)

Property values used for versions:
project.version.main =3D 1.0.1
project.version.full =3D 1.0.1-1

The jar file built looks like ${dist.dir}/my-module-1.0.1.jar but I would l=
ike the ability to publish it as my-module-1.0.1-1.jar in certain cases.

For local publishes I don't care so much about being able to add extra vers=
ion information to identify minor changes i.e. the "-1" part. But it will b=
e useful once I add publishing to a shared repo for automated builds, so I'=
d like to understand whether it is possible. I assumed from reading the doc=
 reference with the different options revision & pubrevision it would be, b=
ut not so sure now.


Tested with the latest 2.2.0 release version as well and same problem exist=
s. I'm sure I'm missing something, I just don't know what.

--
Regards,
Darragh Bailey