- takes advantage of Xalan redirect extension, therefore I don't need extra code to split the document several pieces and process them with different stylesheets.
- now using a strategy to determine a valid Xalan executor at runtime. It first check for Xalan2 then for Xalan1.
As a convenience the Xalan version is displayed in the output.
git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@269504 13f79535-47bb-0310-9956-ffa450edef68
Scott Boag <scott_boag@lotus.com>, Gary Peskin <garyp@firstech.com> and David Marston <david_marston@lotus.com> are aware of this
but the problem is mostly due to specifications ambiguities with locale and default separators...
Just in case I'm redefining the separators used in format-number so that there will be no problems on non-us locale.
git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@269502 13f79535-47bb-0310-9956-ffa450edef68
PR: 2515
Try the less costly File.rename before copying a file byte by byte.
PR: 2424
Submitted by: Magesh Umasankar <umagesh@rediffmail.com>
git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@269486 13f79535-47bb-0310-9956-ffa450edef68
changes
-removed 'owner' attribute from ILASM (it just prints a warning and is
stripped from the docs)
-changed the referenced dlls to the beta-2 set
-added some options to csc:
fullpaths
win32res
noconfig
utf8output
Submitted by: Steve Loughran <steve_l@iseran.com>
git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@269485 13f79535-47bb-0310-9956-ffa450edef68
I must save the files before I commit, I must save the files before I
commit, I must save the files before I commit, I must save the files
before I commit, ...
git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@269484 13f79535-47bb-0310-9956-ffa450edef68
that was redundant, remove some tabs, add testcase that checks that
files don't get overwritten if they'd be identical to the new version.
git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@269474 13f79535-47bb-0310-9956-ffa450edef68
Antcall was broken since the ProjectComponent check is too agressive
Now only applies to data types. The Ant task is perhaps a little special
in that it returns a task for one of its nested elements.
git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@269463 13f79535-47bb-0310-9956-ffa450edef68
to the project object and the ability to log messages through that
project. The IntrospectionHelper cooperates to ensure DataTypes
created as nested elements are correctly setup
git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@269458 13f79535-47bb-0310-9956-ffa450edef68
This is a first cut of the generalization of <available> and
<uptodate> that is on the list for Ant2. This task supports a single
condition and sets a property if it holds true - conditions can be
containers for other conditions in turn, giving it the opportunity to
support boolean logic.
Built in conditions as of now:
* <available> and <uptodate> (slightly modified the tasks to allow them to
be used as conditions)
* containers <and>, <or> and <not>
* New conditions <equals> (compares to Strings) and <os> which should
give easier access to os.name.
More extensive documentation to follow. Take a look at Ant's build
file, it uses the task to detect whether javamail is available now.
I had to perform some ugly tricks to make sure that project gets
passed to every object that will need it - this will be very different
in the future I hope.
git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@269456 13f79535-47bb-0310-9956-ffa450edef68