On Thu, May 6, 2010 at 23:51, Maarten Coene wrote:
> Xavier,
>
> won't this workaround cause every artifact to be copied instead of only the
> modified ones?
>
You're absolutely right.
>
> Maybe we should add an extra attribute (for instance 'overwrite') to the
> retrieve task to indicate what w
Hi,
Antoine
Maarten Coene wrote:
> Xavier,
>
> won't this workaround cause every artifact to be copied instead of only the
> modified ones?
>
>
I need to try the workaround
> Maybe we should add an extra attribute (for instance 'overwrite') to the
> retrieve task to indicate what we want. T
Hi Ed,
thanks for the test case, I'll try to look into the problem.
I guess the problem is that at the moment I'm more or less the only (active)
Ivy committer and I don't have that much spare time, do that's the main reason
that not all issues are addressed as they should.
Maarten
- Ori
Xavier,
won't this workaround cause every artifact to be copied instead of only the
modified ones?
Maybe we should add an extra attribute (for instance 'overwrite') to the
retrieve task to indicate what we want. This attribute could have following
values:
- always: indicates we always want to
Hello Antoine,
On Tue, May 4, 2010 at 04:46, Antoine Levy-Lambert wrote:
> Hello Maarten,
>
> I would be interested in a solution for
> https://issues.apache.org/jira/browse/IVY-1044
>
> I have created where I work a deployment system based on ant and ivy,
> and sometimes the users ... rollback
