Hi again,
> There is already one actually ..., so you can also test the existing
> patch ...
Thanks for reply. I compared the patch to my solution and its exactly the
same way (using mapper for connecting src and dest).
I would appreciate if this patch is included in the next version of ant.
Cha
I concur that this issue should be addressed by fixing the default
behavior even at the risk of backwards compatibility issues - I
seriously doubt that folks would complain about this change.
Erik
On May 27, 2005, at 11:18 AM, Antoine Levy-Lambert wrote:
Matt Benson wrote:
Yes, it a
Matt Benson wrote:
Yes, it appears the patch should default to a
flattenmapper rather than an identitymapper... or did
you have some other concern?
-Matt
Hello Matt,
the image task now seems to contain a kind of hardcoded flattenmapper.
This is not usual for an an ant.task, and I would
--- Antoine Levy-Lambert <[EMAIL PROTECTED]> wrote:
[SNIP]
> I have had a look at the existing code, and I wonder
> whether it will be
> possible to fix the problem while maintaining
> compatibility.
Yes, it appears the patch should default to a
flattenmapper rather than an identitymapper... or d
http://ant.apache.org/ant_task_guidelines.html
--
Jeffrey E. Care ([EMAIL PROTECTED])
WebSphere Build SWAT Team Lead
WebSphere Build Tooling Lead (Project Mantis)
https://w3.opensource.ibm.com/projects/mantis
"Helmut Lerch" <[EMAIL PROTECTED]> wrote on 05/27/2005 03:58:50 AM:
> Hy again,
>
>
Helmut Lerch wrote:
Hy again,
You are not doing anything wrong. Actually, there is a bug report 30373
http://issues.apache.org/bugzilla/show_bug.cgi?id=30373 concerning this
in our bug reporting system. You might want to vote for the bug.
I think I have solved the problems in the sou
Hy again,
> You are not doing anything wrong. Actually, there is a bug report 30373
> http://issues.apache.org/bugzilla/show_bug.cgi?id=30373 concerning this
> in our bug reporting system. You might want to vote for the bug.
I think I have solved the problems in the source code. What is the easie
Hello Helmut,
Helmut Lerch wrote:
Dear all
I have a problem with the image task.
Lets say I have a directory structure like:
${src}/image1/img1.jpg
${src}/image1/img2.jpg
${src}/image2/img3.jpg
${src}/image2/img4.jpg
If I use the image task:
I get the result (with the n
Dear all
I have a problem with the image task.
Lets say I have a directory structure like:
${src}/image1/img1.jpg
${src}/image1/img2.jpg
${src}/image2/img3.jpg
${src}/image2/img4.jpg
If I use the copy task:
I get the result:
${copyPath}/image1/img1.jpg
${copyPath}/image
