[
https://issues.apache.org/jira/browse/IVY-1286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13492351#comment-13492351
]
Dan Leong commented on IVY-1286:
--------------------------------
This issue is affecting our builds too. Ivy 2.2.0, Ant 1.8.4 and Java 1.6.0_31
The problem for us seemed to be an inline ivy:resolve in our run-tests target
in order to load ant-contrib and an internal task helper.
We were doing:-
<ivy:resolve organisation="net.sourceforge.antcontrib"
module="ant-contrib" revision="${ant-contrib.version}" type="jar"
log="download-only" inline="true" keep="true"/>
<ivy:cachepath pathid="antcontrib.ant.path"/>
And we replaced it with
<ivy:cachepath organisation="net.sourceforge.antcontrib"
module="ant-contrib" revision="${ant-contrib.version}" type="jar"
log="download-only" inline="true"
pathid="antcontrib.ant.path"/>
Alternatively we found that adding a "build-tools" config in our ivy.xml
allowed us to remove the inline requirement.
Not sure if this is a bug or intentional behaviour, but any chance of this
getting worked on soon? Or mentioned in the docs if we're using the tool
wrongly...
> publish task ins't working after inline resolve
> -----------------------------------------------
>
> Key: IVY-1286
> URL: https://issues.apache.org/jira/browse/IVY-1286
> Project: Ivy
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.2.0
> Environment: Windwos
> Reporter: Bart Dooms
> Attachments: output.txt
>
>
> The publish task isn't working after inline resolve.
> I used the following instructions in my build.xml file:
> <ivy:resolve refresh="true" *inline="true"* keep="true"
> organisation="${pl.organisation}" module="${pl.module}"
> revision="${ivy.revision}"/>
>
> <ivy:publish pubrevision="${pl.newVersion}"
> resolver="localRepository" forcedeliver="true"
> update="true" merge="false" overwrite="true"
> status="Baselined"
> srcivypattern="${ivy.default.cache.dir}/${ivy.cache.default.ivy.pattern}"
> />
> The resolve task is not taking into account the attribute *keep=true*,
> because in the cache I found the follwoing file:
> resolved-_[organisation]_-_[Module]_-*caller-working*.xml
> And even the publish task is seeking for
> resolved-_[organisation]_-_[Module]_-*caller-working*_@computerName_.xml
> As you can see in the error track trace:
> D:\SVN\trunk\repository\build.xml:203:
> SYS#PythonApi-caller;working@P100003A1: java.lang.IllegalStateException: ivy
> file
> not found in cache for SYS#PythonApi-caller;working@P100003A1: please
> resolve dependencies before delivering (d:\tryout
> \Proba-V\cache\[email protected])
> at
> org.apache.ivy.core.deliver.DeliverEngine.deliver(DeliverEngine.java:112)
> at org.apache.ivy.Ivy.deliver(Ivy.java:586)
> at org.apache.ivy.ant.IvyDeliver.doExecute(IvyDeliver.java:423)
> at org.apache.ivy.ant.IvyTask.execute(IvyTask.java:277)
> at org.apache.ivy.ant.IvyPublish.doExecute(IvyPublish.java:308)
> at org.apache.ivy.ant.IvyTask.execute(IvyTask.java:277)
> at
> org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
> at sun.reflect.GeneratedMethodAccessor5.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:390)
> at org.apache.tools.ant.Target.performTasks(Target.java:411)
> at
> org.apache.tools.ant.Project.executeSortedTargets(Project.java:1397)
> at org.apache.tools.ant.Project.executeTarget(Project.java:1366)
> at
> org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
> at org.apache.tools.ant.Project.executeTargets(Project.java:1249)
> at org.apache.tools.ant.Main.runBuild(Main.java:801)
> at org.apache.tools.ant.Main.startAnt(Main.java:218)
> at org.apache.tools.ant.launch.Launcher.run(Launcher.java:280)
> at org.apache.tools.ant.launch.Launcher.main(Launcher.java:109)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
