ant-apache-log4j-1.7.1-7.5>t  DH`pJh/=„"^H{OL,i\И'j;HjH[0zP\f L9])o68vˎ; υV ۭ'Kf¼ }D)4ejTF9 @cQU18ͬeT$5_l쭔Bͼ `g٨߈n n@`scZ9;cY_OÌʱVYy?|gPV޺G7acb682ea59d435c98d8d9a926cbc7c9de298b9165Jh/=„> D@s=)€쎁,ب1W ~n%eIԧظ)&u*V 2RehVRru CAk*3,snGvzu_icP .ͧ! p<2c֖9Wp0$UaD\m~0"^:,vm]`œȿjn/{4 -G wVPq"# ]uovl2j /fԠQ\/OȀaE8$D?$4d  A "=CLh v    <X{ $(8 9 : B!F!G!H!I"X" Y"Z"8["<\"H]"d^"b#8c#d$e$ f$l$z$$Cant-apache-log4j1.7.17.5Optional apache log4j tasks for antApache Ant is a Java-based build tool. This package contains optional apache log4j tasks for Apache Ant.Jbuild10/openSUSE 11.2openSUSEApache Software License ..http://bugs.opensuse.orgDevelopment/Tools/Buildinghttp://jakarta.apache.org/linuxnoarch # 񁤁AA큤JJJJJJJdcbcb27845ac48c075f1fc9d3da975648664dcc380c0ab9750465eab9cc7540532ed57789ef71ad156412eeac6c21964ant-apache-log4j-1.7.1.jarant-apache-log4j.jarrootrootrootrootrootrootrootrootrootrootrootrootrootrootant-antlr-1.7.1-7.5.src.rpmant-apache-log4jant-jakarta-log4jant-apache-log4j    antlog4jrpmlib(VersionedDependencies)rpmlib(PayloadFilesHavePrefix)rpmlib(CompressedFileNames)rpmlib(PayloadIsLzma)1.7.13.0.3-14.0-13.0.4-14.4.6-14.7.1Jd\@J8I@IHf@H}H!G!FF.F@f@E@coolo@novell.commvyskocil@suse.czro@suse.demvyskocil@suse.czmvyskocil@suse.czcoolo@suse.demvyskocil@suse.czcoolo@suse.dedbornkessel@suse.dedbornkessel@suse.dedbornkessel@suse.dedbornkessel@suse.de- build against log4j-mini to avoid build cycle- do not use Release number in Requires of subpackages- do not assume release number for ant and ant-antlr are identical- update to 1.7.1. Upstream changes (full list is in WHATSNEW): * String resources only have properties single expanded. If you relied on resources being expanded more than once, it no longer happens. Bugzilla report 42277. * A String resource's encoding attribute was only taken into account when set from the resource's OutputStream; the InputStream provided the String's binary content according to the platform's default encoding. Behavior has been modified to encode outgoing (InputStream) content as well as encoding incoming (OutputStream) content. * with fork now returns gives -1 instead of 0 as result when * failonerror is false and some exception (including timeout) occurs. Br 42377. * ant-type attribute has been marked as deprecated and a warning has been issued if it is encountered in the build file. * FileUtils.createTempFile now actually creates the file. The TempFile task still does not create the file by default, can be instructed to do so however using a new parameter. Bugzilla report 33969. - added maven pom files from jpackage project - synchronized ant.spec with jpackage.org 5.0 - used ant-antlr-prepare.sh for generate of ant-antlr.spec from ant.spec to keep them synchronized. Build is branched using value of %%bootstrap macro: * bootstrap == 1 means build ant, ant-{jmf,nodeps,scripts,swing,trax} * bootstrap == 0 means build rest of ant modules + ant-javadoc- use a antlr-bootstrap do avoid another cycle- avoid another build cycle- build using gcj, to allow a openjdk6 bootstrap - change a source and a target level to 1.5 in build.xml- fix changelog for build service- add links to jar files in /usr/share/ant/lib- make packages noarch, as jai was removed - update to version 1.7.0 major changes are (for a complete list, consult /usr/share/doc/packages/ant/WHATSNEW): Changes that could break older environments: - ------------------------------------------ * Initial support for JDK 6 (JSR 223) scripting. <*script*> tasks will now use javax.scripting if BSF is not available, or if explicitly requested by using a "manager" attribute. * The -noproxy option which was in the previous 1.7 alpha and beta releases has been removed. It is the default behavior and not needed. * Removed launcher classes from nodeps jar. * filter reader uses ISO-8859-1 encoding to read the java class file. Bugzilla report 33604. * Defer reference process. Bugzilla 36955, 34458, 37688. This may break build files in which a reference was set in a target which was never executed. Historically, Ant would set the reference early on, during parse time, so the datatype would be defined. Now it requires the reference to have been in a bit of the build file which was actually executed. If you get an error about an undefined reference, locate the reference and move it somewhere where it is used, or fix the depends attribute of the target in question to depend on the target which defines the reference/datatype. *