Hi Matthias,
On Jul 20, 2009, at 1:31 PM, Hans Dockter wrote:
Hi Matthias,
On Jul 20, 2009, at 10:02 AM, Pfau, Matthias wrote:
Hi together,
I already published to an ivy repo using older gradle releases, but
certainly fell into a trap with 0.6.1: The uploaded ivy.xml always
contains an absolute path:
[...]
<publications>
<artifact name="war-test" type="jar" ext="jar" conf="archives"
filePath="C:\tools\workspace\war-test\build\libs\war-test-0.2.jar"/>
</publications>
[...]
Unfortunately, ivy does not accept this declaring a dependency to
such an artifact.
Ivy's error message:
Attribute 'filePath' is not allowed to appear in element 'artifact'.
Any ideas on this?
As a work around you can set validate to false for the resolvers in
the ivysettings.xml of the retrieving build:
<ivysettings>
<settings defaultResolver="main"/>
<resolvers>
<filesystem name="main" validate="false">
...
We anyway need to get rid of the filepath attribute in the published
ivy.xml. Could you file a Jira for this with fix for 0.7.1?
This is now fixed in trunk and branch.
- Hans
--
Hans Dockter
Gradle Project Manager
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
