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 | [EMAIL PROTECTED] ] :: 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 | [EMAIL PROTECTED] ]: missing published artifacts for [ jbpm | enterprise | [EMAIL PROTECTED] ]: [[ 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.

Reply via email to