On 29/04/2013 17:10, carsten.pfeif...@gebit.de wrote:
Hi,
Is there a way to prevent the deliver (publish) task from overwriting
the source ivy.xml file?
I have a bunch of project directories like this
projectx
- src
- dist
- ivy.xml
Now when I publish these projects, the original
Hey Carsten,
With option 2 are you already specifying the srcivypattern? In theory if
you've already called resolve, and you specify the srcivypattern for
publish pointing to a non-existent location e.g.
/home/carsten/projects/projectx/dist/ivy.xml
Ivy should use the source file
Hi Jason,
my problem is that I do not want to have the ivy.xml inside the dist/
directory.
For some of the projects, I do not even have a separate dist/ directory.
That's
why I point srcivypattern to a temporary location.
But I thought that srcivypattern should actually point to an existing
I'll check if Ivy will indeed create that copy automatically for me.
That worked! So I only need to specify srcivypattern to some temporary
file.
Thanks
Carsten
From: carsten.pfeif...@gebit.de
To: ivy-user@ant.apache.org
Date: 30.04.2013 11:29
Subject:Re: deliver overwriting
That's good news! Am I understanding that you don't want the resolved
Ivy file at all?
In that case can you just set publishivy=false on the publish task?
Jason
On 30/04/2013 10:34, carsten.pfeif...@gebit.de wrote:
I'll check if Ivy will indeed create that copy automatically for me.
That
I want to have the Ivy file published in the repository, but I don't need
the intermediate copy in the dist/ folder
(or anywhere else). I would have expected that the Ivy file would be
- put into the cache
- published to the repository
I don't need the third copy :-) I understand that some
I'm with you, there is no need for the local copy in that scenario and
it's just an additional item for your build to have to clean up.
All the best.
Jason
On 30/04/2013 10:44, carsten.pfeif...@gebit.de wrote:
I want to have the Ivy file published in the repository, but I don't need
the
