duplicate (attribute): behavior when a duplicate file is found. Valid values are add, preserve, and fail. The default value is add.
zipgroupfileset (nested fileset): allows for multiple zip files to be merged into the archive. Each file found in this fileset is added to the archive the same way that "zipfileset src" files are added.
Jar task
duplicate/zipgroupfileset: same as in Zip task
filesetmanifest (attribute): behavior when a Manifest is found in a zipfileset or zipgroupfileset file is found. Valid values are skip, merge, and mergewithoutmain. mergewill merge all of manifests together, and merge this into any other specified manifests mergewithoutmain merges everything but the Main section of the manifests. Default value is skip
manifest (existing attribute): this attribute now also accepts the name of a jar added through a fileset. If its the name of an added jar, the task expects the manifest to be in the jar at META-INF/Manifest.mf
Submitted by: Brian Deitte <bdeitte@macromedia.com>
PR: 5667, 5036
git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@271698 13f79535-47bb-0310-9956-ffa450edef68
Other code cleanup (axing "m_" prefixes).
Added "unit" attribute to <entry> defaulting to DAY. This was essentially the previous default, but it was far too confusing.
Test cases beefed up to consider several scenarios.
There may be more changes needed to satisfy other use cases, and certainly some previous (undocumented) behavior has been changed (for the better!).
Is there a use-case for "never" as a value?
git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@271503 13f79535-47bb-0310-9956-ffa450edef68
1. New tests for the DemuxOutputStream and parallel task
2. Fix for the DemuxOutputStream thread problem identified by Jon Skeet
3. Found additional bug where UnknownElement does not hand output and error
strings onto the real task
A little bit of checkstyling.
Hmmm, really should be in bed.
git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@271501 13f79535-47bb-0310-9956-ffa450edef68
XP-style: added test case to detect bug, then fixed it. Also, trying to break out of the mould of the "testN" test case names - too brittle and non-descriptive.
git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@271143 13f79535-47bb-0310-9956-ffa450edef68
the Jakarta style. Those are the stylesheets used to generate reports for audit, metrics, coverage
recently sent to ant-dev
git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@271127 13f79535-47bb-0310-9956-ffa450edef68
(1) Make sure all years in which a file has been modified are
listed.
(2) Make sure the format is consistent, i.e. separate consecutive
years with a dash, not a comma.
Also: the initial checkin into this CVS module was in 2000, not 1999.
git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@270657 13f79535-47bb-0310-9956-ffa450edef68
that controls implicit copying of references - i.e. we don't copy
anything by default.
Try to copy a clone before copying the real object.
inheritRefs="true" doesn't make any sense for <antcall> as all
references of the calling project will be defined in the new project
and wouldn't be overwritten. That's why <antcall> didn't even get
this attribute.
git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@270136 13f79535-47bb-0310-9956-ffa450edef68
Made sure that operations internal to Project could not generate these warnings by adding a new setPropertyInternal method that didn't do any checks.
Also made the getUserProperties and getProperties methods return copies of maps rather than direct references.
Updated WHATSNEW to warn about these issues.
Added some unit tests to verify that property immutability is enforced - where we actually do enforce it ;)
Submitted by: "Erik Hatcher" <jakarta-ant@ehatchersolutions.com>
git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@270078 13f79535-47bb-0310-9956-ffa450edef68