Mailing-List: contact ivy-user-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ivy-user@ant.apache.org
Received-SPF: pass (athena.apache.org: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com;
  h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type;
  b=l+DWZH2w10ssFCM9ZbEOuHuBtYaNX0Bl1muJnplwtG6ZWnn+JJJN/5a+/vuJjoxybSgsTGs5zeGaKR/9tX0N1UmKJEc4+1ftO+mWsFRsfiBZ8SIn0nsDwj5kJmKTEtSUI1669VQW0aHCk1ukz5wL69dnRTmIvwiZT5hI8HvhNLA=;
Message-ID: <284026.72754.qm@web30801.mail.mud.yahoo.com>
References: <A8E7B425-B33C-49DD-90BD-01EC9B8B589B@yahoo.co.uk>
 <AANLkTik194Yz3frM-ueRqUanVBt8r_hUiTitRT=GvXTY@mail.gmail.com>
 <62BA0B5D-EC6B-4871-AE25-38DB48185070@yahoo.co.uk>
 <B67DB998-7833-4DCD-90E3-4683BBE15D2F@yahoo.co.uk>
 <4C14046A-AC40-4754-8565-4849D39F1F62@yahoo.co.uk>
 <AANLkTimv_gd0=yotw7abiRb9nHr9aqx-Ckdaa9aORmvt@mail.gmail.com>
 <F8CDFE3D-7DFC-41D8-B6D2-05E4703DDF39@yahoo.co.uk>
 <579370.15238.qm@web30805.mail.mud.yahoo.com>
 <3F8CE9F4-167D-4E8E-B236-E7A268E7019F@yahoo.co.uk>
 <940720.1713.qm@web30803.mail.mud.yahoo.com>
 <E1CEE23B-B557-402A-BE17-5AB33211480C@yahoo.co.uk>
 <335661.49304.qm@web30805.mail.mud.yahoo.com>
 <7E419B97-45CD-4251-A420-4CD2465349C9@yahoo.co.uk>
Date: Thu, 26 Aug 2010 13:07:40 -0700 (PDT)
From: Maarten Coene <maarten_coene@yahoo.com>
Subject: Re: Reference build-path not found.
To: ivy-user@ant.apache.org
In-Reply-To: <7E419B97-45CD-4251-A420-4CD2465349C9@yahoo.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

Ivy is looking for the jar "testproject-baseserver-common.jar" in your 
${build.dir} directory.
Are you sure it is in there?

Maarten


----- Original Message ----
From: Ben Cuthbert <ben_cuthbert@yahoo.co.uk>
To: ivy-user@ant.apache.org
Sent: Thu, August 26, 2010 9:59:25 PM
Subject: Re: Reference build-path not found.

Thanks Maarten

I changed what you suggested. Looks a bit closer. The IO exception in debug I 
can't see the directory it is looking for the jar in


<target name="publish-remote" depends="version" description="--> publish this 
project in the ivy repository">
        <ivy:publish artifactspattern="${build.dir}/[artifact].[ext]" 
                           resolver="artifactory-publish"
                           pubrevision="${version}" 
                           status="integration"
                           overwrite="true"
        />
        <echo message="project ${ant.project.name} released with version 
${version}" />
    </target>
testproject
/Users/cuthbe/dev/code/testproject-trunk/build/build_common.xml:162: impossible 
to publish artifacts for 
com.testproject#testproject-baseserver-common;working@cuthbes-macbook.local: 
java.io.IOException: missing artifact 
com.testproject#testproject-baseserver-common;1.0!testproject-baseserver-common.jar

    at 
org.apache.tools.ant.ProjectHelper.addLocationToBuildException(ProjectHelper.java:508)

    at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:418)
    at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
    at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
    at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

    at java.lang.reflect.Method.invoke(Method.java:597)
    at 
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
    at org.apache.tools.ant.Task.perform(Task.java:348)
    at org.apache.tools.ant.taskdefs.Sequential.execute(Sequential.java:62)
    at net.sf.antcontrib.logic.IfTask.execute(Unknown Source)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

    at java.lang.reflect.Method.invoke(Method.java:597)
    at 
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
    at org.apache.tools.ant.TaskAdapter.execute(TaskAdapter.java:154)
    at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
    at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
    at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

    at java.lang.reflect.Method.invoke(Method.java:597)
    at 
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
    at org.apache.tools.ant.Task.perform(Task.java:348)
    at org.apache.tools.ant.Target.execute(Target.java:357)
    at org.apache.tools.ant.Target.performTasks(Target.java:385)
    at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337)
    at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
    at 
org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)

    at org.apache.tools.ant.Project.executeTargets(Project.java:1189)
    at org.apache.tools.ant.Main.runBuild(Main.java:758)
    at org.apache.tools.ant.Main.startAnt(Main.java:217)
    at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257)
    at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104)


On 26 Aug 2010, at 20:50, Maarten Coene wrote:

> I think it is caused by your empty <artifacts /> element.
> Please remove that from your ivy:publish task, something like should work:
> 
>        <ivy:publish artifactspattern="${build.dir}/[artifact].[ext]" 
>                           resolver="remoterepo-publish"
>                           pubrevision="${version}" 
>                           status="integration"
>                           overwrite="true" />
> 
> Maarten
> 
> 
> 
> ----- Original Message ----
> From: Ben Cuthbert <ben_cuthbert@yahoo.co.uk>
> To: ivy-user@ant.apache.org
> Sent: Wed, August 25, 2010 9:35:40 AM
> Subject: Re: Reference build-path not found.
> 
> I think I am getting closer. So I have the ant build downloading ivy from the 
> maven repo each time and putting it in the classpath. 
> 
> So now I see this in the ant log
> 
> Setting project property: ivy.shared.default.root -> ${repository.dir}/shared
> parsing buildfile 
>jar:file:/Users/cuthbe/applications/apache-ant-1.7.1/lib/ivy-2.2.0-rc1.jar!/org/apache/ivy/ant/antlib.xml
>l
> with URI = 
>jar:file:/Users/cuthbe/applications/apache-ant-1.7.1/lib/ivy-2.2.0-rc1.jar!/org/apache/ivy/ant/antlib.xml
>l
> 
> 
> 
> And then way down the bottom I see
> 
> publish-remote:
> Overriding previous definition of property "ivy.version"
> Setting project property: ivy.version -> 2.2.0-rc1
> [ivy:publish] parameter found as ivy variable: 
ivy.organisation=com.testproject
> [ivy:publish] parameter found as ivy variable: 
> ivy.module=testproject-baseserver-common
> [ivy:publish] parameter found as ivy variable: 
> ivy.revision=working@cuthbes-macbook.local
> [ivy:publish] parameter not found: ivy.deliver.branch
> [ivy:publish] parameter found as attribute value: ivy.deliver.revision=1.0
> [ivy:publish] parameter found as attribute value: ivy.status=integration
> [ivy:publish] :: publishing :: com.testproject#testproject-baseserver-common
> [ivy:publish]     validate = true
> [ivy:publish] post 1.3 ivy file: using exact as default matcher
>  [antcall] Exiting 
>/Users/cuthbe/dev/code/testproject-trunk/testproject-baseserver-common/build.xml.
>.
> 
>      [ant] Exiting 
>/Users/cuthbe/dev/code/testproject-trunk/testproject-baseserver-common/build.xml.
>.
> 
> 
> BUILD FAILED
> /Users/cuthbe/dev/code/testproject-trunk/build/build.xml:183: The following 
> error occurred while executing this line:
>/Users/cuthbe/dev/code/testproject-trunk/testproject-baseserver-common/build.xml:14:
>:
> The following error occurred while executing this line:
> /Users/cuthbe/dev/code/testproject-trunk/build/build_common.xml:162: impossible 
>
> to publish artifacts for 
> com.testproject#testproject-baseserver-common;working@cuthbes-macbook.local: 
> java.lang.NullPointerException
>    at 
>org.apache.tools.ant.ProjectHelper.addLocationToBuildException(ProjectHelper.java:508)
>)
> 
>    at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:418)
>    at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
>    at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
>    at 
>sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>)
> 
>    at java.lang.reflect.Method.invoke(Method.java:597)
>    at 
> org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
>    at org.apache.tools.ant.Task.perform(Task.java:348)
>    at org.apache.tools.ant.taskdefs.Sequential.execute(Sequential.java:62)
>    at net.sf.antcontrib.logic.IfTask.execute(Unknown Source)
>    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>    at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>    at 
>sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>)
> 
>    at java.lang.reflect.Method.invoke(Method.java:597)
>    at 
> org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
>    at org.apache.tools.ant.TaskAdapter.execute(TaskAdapter.java:154)
>    at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
>    at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
>    at 
>sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>)
> 
>    at java.lang.reflect.Method.invoke(Method.java:597)
>    at 
> org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
>    at org.apache.tools.ant.Task.perform(Task.java:348)
>    at org.apache.tools.ant.Target.execute(Target.java:357)
>    at org.apache.tools.ant.Target.performTasks(Target.java:385)
>    at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337)
>    at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
>    at 
>org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
>)
> 
>    at org.apache.tools.ant.Project.executeTargets(Project.java:1189)
>    at org.apache.tools.ant.Main.runBuild(Main.java:758)
>    at org.apache.tools.ant.Main.startAnt(Main.java:217)
>    at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257)
>    at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104)
> 
> 
> Before the above error I do see loads of HTTP requests to the repo
> 
> Setting project property: ivy.version -> 2.2.0-rc1
> [ivy:buildnumber]     using local to list all in 
> /Users/cuthbe/.ivy2/cache/com.testproject/testproject-baseserver-common/ivys
> [ivy:buildnumber]         found 3 urls
> [ivy:buildnumber]         1 matched 
>/Users/cuthbe/.ivy2/cache/com.testproject/testproject-baseserver-common/ivys/ivy-[revision].xml
>l
> 
> [ivy:buildnumber] local do not support transaction. ivy pattern does not use 
> revision as a directory
> [ivy:buildnumber]     using local to list all in 
> /Users/cuthbe/.ivy2/cache/com.testproject/testproject-baseserver-common/jars
> [ivy:buildnumber]         found 3 urls
> [ivy:buildnumber]         0 matched 
>/Users/cuthbe/.ivy2/cache/com.testproject/testproject-baseserver-common/jars/[artifact]-[revision].jar
>r
> 
> [ivy:buildnumber] HTTP response status: 404 
>url=http://192.168.2.4:9999/artifactory/libs-releases-local/com/testproject/testproject-baseserver-common/maven-metadata.xml
>l
> 
> [ivy:buildnumber] CLIENT ERROR: File not found. 
>url=http://192.168.2.4:9999/artifactory/libs-releases-local/com/testproject/testproject-baseserver-common/maven-metadata.xml
>l
> 
> [ivy:buildnumber]     maven-metadata not available: 
>http://192.168.2.4:9999/artifactory/libs-releases-local/com/testproject/testproject-baseserver-common/maven-metadata.xml
>l
> 
> [ivy:buildnumber]     using libs-releases-local to list all in 
>http://192.168.2.4:9999/artifactory/libs-releases-local/com/testproject/testproject-baseserver-common/
>/
> 
> [ivy:buildnumber] HTTP response status: 404 
>url=http://192.168.2.4:9999/artifactory/libs-releases-local/com/testproject/testproject-baseserver-common/
>/
> 
> [ivy:buildnumber] CLIENT ERROR: Not Found 
>url=http://192.168.2.4:9999/artifactory/libs-releases-local/com/testproject/testproject-baseserver-common/
>/
> 
> [ivy:buildnumber] problem while listing resources in 
>http://192.168.2.4:9999/artifactory/libs-releases-local/com/testproject/testproject-baseserver-common/
>/
> with libs-releases-local:
> [ivy:buildnumber]  java.io.IOException The HTTP response code for 
>http://192.168.2.4:9999/artifactory/libs-releases-local/com/testproject/testproject-baseserver-common/
>/
> did not indicate a success. See log for more detail.
> [ivy:buildnumber] HTTP response status: 404 
>url=http://192.168.2.4:9999/artifactory/testproject-release/com/testproject/testproject-baseserver-common/maven-metadata.xml
>l
> 
> [ivy:buildnumber] CLIENT ERROR: File not found. 
>url=http://192.168.2.4:9999/artifactory/testproject-release/com/testproject/testproject-baseserver-common/maven-metadata.xml
>l
> 
> [ivy:buildnumber]     maven-metadata not available: 
>http://192.168.2.4:9999/artifactory/testproject-release/com/testproject/testproject-baseserver-common/maven-metadata.xml
>l
> 
> [ivy:buildnumber]     using testprojectrepo-publish to list all in 
>http://192.168.2.4:9999/artifactory/testproject-release/com/testproject/testproject-baseserver-common/
>/
> 
> [ivy:buildnumber] HTTP response status: 404 
>url=http://192.168.2.4:9999/artifactory/testproject-release/com/testproject/testproject-baseserver-common/
>/
> 
> [ivy:buildnumber] CLIENT ERROR: Not Found 
>url=http://192.168.2.4:9999/artifactory/testproject-release/com/testproject/testproject-baseserver-common/
>/
> 
> [ivy:buildnumber] problem while listing resources in 
>http://192.168.2.4:9999/artifactory/testproject-release/com/testproject/testproject-baseserver-common/
>/
> with testprojectrepo-publish:
> [ivy:buildnumber]   java.io.IOException The HTTP response code for 
>http://192.168.2.4:9999/artifactory/testproject-release/com/testproject/testproject-baseserver-common/
>/
> did not indicate a success. See log for more detail.
> [ivy:buildnumber]     maven-metadata not available: 
>http://192.168.2.4:9999/artifactory/testproject-release/com/testproject/testproject-baseserver-common/maven-metadata.xml
>l
> 
> [ivy:buildnumber]     using testprojectrepo-publish to list all in 
>http://192.168.2.4:9999/artifactory/testproject-release/com/testproject/testproject-baseserver-common/
>/
> 
> [ivy:buildnumber] HTTP response status: 404 
>url=http://192.168.2.4:9999/artifactory/testproject-release/com/testproject/testproject-baseserver-common/
>/
> 
> [ivy:buildnumber] CLIENT ERROR: Not Found 
>url=http://192.168.2.4:9999/artifactory/testproject-release/com/testproject/testproject-baseserver-common/
>/
> 
> [ivy:buildnumber] problem while listing resources in 
>http://192.168.2.4:9999/artifactory/testproject-release/com/testproject/testproject-baseserver-common/
>/
> with testprojectrepo-publish:
> [ivy:buildnumber]   java.io.IOException The HTTP response code for 
>http://192.168.2.4:9999/artifactory/testproject-release/com/testproject/testproject-baseserver-common/
>/
> did not indicate a success. See log for more detail.
> [ivy:buildnumber]     using local to list all in 
> /Users/cuthbe/.ivy2/cache/com.testproject/testproject-baseserver-common/ivys
> [ivy:buildnumber]         found 3 urls
> [ivy:buildnumber]         1 matched 
>/Users/cuthbe/.ivy2/cache/com.testproject/testproject-baseserver-common/ivys/ivy-[revision].xml
>l
> 
> [ivy:buildnumber]     using local to list all in 
> /Users/cuthbe/.ivy2/cache/com.testproject/testproject-baseserver-common/jars
> [ivy:buildnumber]         found 3 urls
> [ivy:buildnumber]         0 matched 
>/Users/cuthbe/.ivy2/cache/com.testproject/testproject-baseserver-common/jars/[artifact]-[revision].jar
>r
> 
> [ivy:buildnumber]     maven-metadata not available: 
>http://192.168.2.4:9999/artifactory/libs-releases-local/com/testproject/testproject-baseserver-common/maven-metadata.xml
>l
> 
> [ivy:buildnumber]     using libs-releases-local to list all in 
>http://192.168.2.4:9999/artifactory/libs-releases-local/com/testproject/testproject-baseserver-common/
>/
> 
> [ivy:buildnumber] HTTP response status: 404 
>url=http://192.168.2.4:9999/artifactory/libs-releases-local/com/testproject/testproject-baseserver-common/
>/
> 
> [ivy:buildnumber] CLIENT ERROR: Not Found 
>url=http://192.168.2.4:9999/artifactory/libs-releases-local/com/testproject/testproject-baseserver-common/
>/
> 
> [ivy:buildnumber] problem while listing resources in 
>http://192.168.2.4:9999/artifactory/libs-releases-local/com/testproject/testproject-baseserver-common/
>/
> with libs-releases-local:
> [ivy:buildnumber]   java.io.IOException The HTTP response code for 
>http://192.168.2.4:9999/artifactory/libs-releases-local/com/testproject/testproject-baseserver-common/
>/
> did not indicate a success. See log for more detail.
> Setting project property: ivy.new.revision -> ${module.version.target}-dev-b1
> Setting project property: ivy.new.build.number -> 1
> 
> version:
>    [mkdir] Skipping 
> /Users/cuthbe/dev/code/testproject-trunk/testproject-baseserver-common/build 
> because it already exists.
> [property] Loading 
>/Users/cuthbe/dev/code/testproject-trunk/testproject-baseserver-common/build/testproject-baseserver-common.properties
>s
> 
> Property "module.version.target" has not been set
> Override ignored for property "version"
> 
> 
> 
> On 24 Aug 2010, at 21:08, Maarten Coene wrote:
> 
>> Are you sure this stacktrace is from the ivy-2.2.0-rc1 release?
>> 
>> IvyPatternHelper.java:241 (the place where the NPE happens) is an empty line in 
>>
>> 
>> this release:
>>http://svn.apache.org/viewvc/ant/ivy/core/tags/2.2.0-rc1/src/java/org/apache/ivy/core/IvyPatternHelper.java?revision=959425&view=markup
>>p
>> p
>> 
>> 
>> Maarten
>> 
>> 
>> 
> 
> 
>