Author: jhm
Date: Wed Jan 10 04:08:28 2007
New Revision: 494793
URL: http://svn.apache.org/viewvc?view=revrev=494793
Log:
Use the style like on the other examples.
Modified:
ant/core/trunk/docs/manual/CoreTypes/mapper.html
Modified: ant/core/trunk/docs/manual/CoreTypes/mapper.html
URL:
Author: jhm
Date: Wed Jan 10 04:12:44 2007
New Revision: 494794
URL: http://svn.apache.org/viewvc?view=revrev=494794
Log:
Add separators between the mappers for easier reading of the source code. (Like
it was before Script Mapper and Filter Mapper).
Modified:
I have an AntLib for which I wrote a FileNameMapper.
I cant use that mapper from inside the antlib.xml:
antlib.xml
---8888888---
-8-
antlib
macrodef name=mask
attribute name=dir/
sequential
move todir=@{dir}
Hi,
I have submitted the following problem to the Maven mailing list which
redirected me to this Ant mailing list.
The problem occurs when I use the maven ant task 2.0.4 with Ant 1.7.0.
The fileset created by the maven:dependencies task raises a
NullPointerException when used in the Ant
That looks like a bug in the Maven task. The only way
for an NPE to be triggered here would seem to indicate
the task passed null as the project argument to
getDirectoryScanner(). Looking at Ant 1.6.5's code it
appears that the same exception would be thrown,
however, so I am confused how this
Sorry... to go farther down the stacktrace, I should
correct myself: it appears that the Maven guys don't
set a project on their fileset when they create it, or
something. So it's a bug for them, but possibly a
regression for Ant after all, if you want to look at
it that way.
-Matt
--- Matt
It looks like it is some strange stuff with
path through the code that just avoids an NPE in ant.1.6.5.
On ant 1.6.5 with the following file and the maven jar in lib,
the first echo works but the second echo fails:
project name=test-maven default=test
--- Peter Reilly [EMAIL PROTECTED] wrote:
It looks like it is some strange stuff with
path through the code that just avoids an NPE in
ant.1.6.5.
[SNIP]
I am not sure how to fix this in ant.
I've got it. It is indeed a case of the Maven code
not having set Project references on their
Author: mbenson
Date: Wed Jan 10 11:46:47 2007
New Revision: 494952
URL: http://svn.apache.org/viewvc?view=revrev=494952
Log:
move and publish public static Project getProject(Object)
Modified:
ant/core/trunk/src/main/org/apache/tools/ant/ComponentHelper.java
Author: mbenson
Date: Wed Jan 10 11:48:57 2007
New Revision: 494953
URL: http://svn.apache.org/viewvc?view=revrev=494953
Log:
when child resource collection added with null Project, it inherits ours
Modified:
Author: mbenson
Date: Wed Jan 10 12:38:55 2007
New Revision: 494970
URL: http://svn.apache.org/viewvc?view=revrev=494970
Log:
document null Project reference bug
Modified:
ant/core/trunk/WHATSNEW
Modified: ant/core/trunk/WHATSNEW
URL:
Author: mbenson
Date: Wed Jan 10 14:34:45 2007
New Revision: 495014
URL: http://svn.apache.org/viewvc?view=revrev=495014
Log:
as discussed on dev@, allow mapper refid to refer to a FileNameMapper
Added:
ant/core/trunk/src/tests/antunit/types/mapper-ref.xml (with props)
Modified:
Hi Matt,
I have checked in code to fix this. Those
experiencing the problem might want to test against a
build from SVN HEAD to verify the problem is fixed for
them. It wouldn't hurt to remind the Maven folks to
set the Project instance on artifacts they create,
either.
That was quick! And
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=41345.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
14 matches
Mail list logo
