You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ivy-user@ant.apache.org by Tom Baeyens <tb...@redhat.com> on 2007/10/17 11:00:57 UTC

published artifacts not found with ant task

When a publish is being invoked from another build file with the ant task like e.g.

<ant dir="../enterprise" target="publish" inheritall="false" />

it seems that ivy doesn't find the published artifacts:

jar:
       [jar] Building jar: C:\wstempranillo\enterprise\target\pvm-enterprise.jar
cfg.jar:
       [jar] Building jar: C:\wstempranillo\enterprise\target\pvm-enterprise-cfg.jar
...
publish:
   [publish] :: delivering :: [ jbpm | enterprise | working@lightning ] :: snapshot 
:: integration :: Wed Oct 17 09:41:57 CEST 2007
   [publish] 	delivering ivy file to target/ivy.xml
   [publish] :: publishing :: [ jbpm | enterprise ]
   [publish] missing artifact [ jbpm | enterprise | snapshot 
]/pvm-enterprise-cfg.jar[jar]:
   [publish] 	target\pvm-enterprise-cfg.jar file does not exist
   [publish] missing artifact [ jbpm | enterprise | snapshot ]/pvm-enterprise.jar[jar]:
   [publish] 	target\pvm-enterprise.jar file does not exist
   [publish] 	published ivy to C:\Documents and 
Settings\tom\.ivy2/local/jbpm/enterprise/snapshot/ivys/ivy.xml

BUILD FAILED
C:\wstempranillo\pvm\build.all.xml:11: The following error occurred while executing 
this line:
C:\wstempranillo\pvm\build.base.xml:115: impossible to publish artifacts for [ jbpm | 
enterprise | working@lightning ]: missing published artifacts for [ jbpm | enterprise 
| working@lightning ]: [[ jbpm | enterprise | snapshot ]/pvm-enterprise-cfg.jar[jar], 
[ jbpm | enterprise | snapshot ]/pvm-enterprise.jar[jar]]


When the same publish target is called directly in the right build file, it works 
fine.  Only when it is called from another build file with the ant task, it fails.

I've tried various combinations of specifying the inheritall and inheritrefs 
attributes in the ant task.  Also I tried the dir attribute in various ways.

-- 
regards, tom.

Re: published artifacts not found with ant task

Posted by Gilles Scokart <gs...@gmail.com>.
There is a few issues about the handling of the relative paths.  You can
look (and maybe vote) to https://issues.apache.org/jira/browse/IVY-387 or on
of the related issue.

Gilles

2007/10/17, Jing Xue <ji...@digizenstudio.com>:
>
> On Wed, Oct 17, 2007 at 11:00:57AM +0200, Tom Baeyens wrote:
> [snip]
> > <ant dir="../enterprise" target="publish" inheritall="false" />
> [snip]
> >   [publish] missing artifact [ jbpm | enterprise | snapshot
> > ]/pvm-enterprise-cfg.jar[jar]:
> >   [publish]   target\pvm-enterprise-cfg.jar file does not exist
> >   [publish] missing artifact [ jbpm | enterprise | snapshot
> >   ]/pvm-enterprise.jar[jar]:
> >   [publish]   target\pvm-enterprise.jar file does not exist
> [snip]
> > When the same publish target is called directly in the right build file,
> it
> > works fine.  Only when it is called from another build file with the ant
> > task, it fails.
> >
> > I've tried various combinations of specifying the inheritall and
> > inheritrefs attributes in the ant task.  Also I tried the dir attribute
> in
> > various ways.
>
> I don't think either of those attributes changes how relative paths(e.g.
> thhe one you likely are using for artifact pattern when calling
> ivy:publish) are handled in an ant call. Maybe try somehow form an
> absolute path for the artifact pattern?
>
> HTH.
> --
> Jing Xue
>



-- 
Gilles SCOKART

Re: published artifacts not found with ant task

Posted by Jing Xue <ji...@digizenstudio.com>.
On Wed, Oct 17, 2007 at 11:00:57AM +0200, Tom Baeyens wrote:
[snip]
> <ant dir="../enterprise" target="publish" inheritall="false" />
[snip]
>   [publish] missing artifact [ jbpm | enterprise | snapshot 
> ]/pvm-enterprise-cfg.jar[jar]:
>   [publish] 	target\pvm-enterprise-cfg.jar file does not exist
>   [publish] missing artifact [ jbpm | enterprise | snapshot 
>   ]/pvm-enterprise.jar[jar]:
>   [publish] 	target\pvm-enterprise.jar file does not exist
[snip]
> When the same publish target is called directly in the right build file, it 
> works fine.  Only when it is called from another build file with the ant 
> task, it fails.
> 
> I've tried various combinations of specifying the inheritall and 
> inheritrefs attributes in the ant task.  Also I tried the dir attribute in 
> various ways.

I don't think either of those attributes changes how relative paths(e.g.
thhe one you likely are using for artifact pattern when calling
ivy:publish) are handled in an ant call. Maybe try somehow form an
absolute path for the artifact pattern?

HTH.
-- 
Jing Xue