On 11/05/2010 2:56 AM, Stefan Bodewig wrote:
On 2010-05-10, Bruce Atherton wrote:
1) On Concat, add an overwrite attribute and mark the force
attribute as deprecated with a warning
2) Add force to copy, echo, etc
3) add forceReadOnly to Concat
this is now the case in trunk
On 2010-05-10, Bruce Atherton wrote:
> What a pain. But given enough time we can fix this:
> 1) On Concat, add an overwrite attribute and mark the force
> attribute as deprecated with a warning
> 2) Add force to copy, echo, etc
> 3) add forceReadOnly to Concat
this is now the case i
On 10/05/2010 8:27 AM, Stefan Bodewig wrote:
you won't like what I'm going to say 8-)
Oh man, it is never easy, is it?
The following non-deprecated tasks use copyFile or copyResource as well:
, the WebLogic deployment tool,,. and
.
For most of them I'd be willing to accept the backward
On 2010-05-07, Bruce Atherton wrote:
> On 07/05/2010 7:52 AM, Stefan Bodewig wrote:
> I'm a big fan of a little consistency.
you won't like what I'm going to say 8-)
>> I see several options:
>> (2) Add a new attribute that controls whether read-only files should be
>> overwritten (let's
On 07/05/2010 7:52 AM, Stefan Bodewig wrote:
First of all I must admit that I like the idea of not overwriting
read-only files better than the old behavior.
Agreed. Although it breaks backward compatibility to change this, it so
violates POLA[1] that I think it needs changing.
Independe
Stefan Bodewig wrote:
Hi all,
it seems we have a difference in behavior between FileChannel and
FileOutputStream that manifests itself in .
When using streams - i.e. Ant prior to 1.8.0 or when filtering - Ant
will happiliy overwrite read-only destination files if the source file
is newer. When
Hi all,
it seems we have a difference in behavior between FileChannel and
FileOutputStream that manifests itself in .
When using streams - i.e. Ant prior to 1.8.0 or when filtering - Ant
will happiliy overwrite read-only destination files if the source file
is newer. When using channels it will
