pool/ant
SHA256
6
0
Fork 1
Code Issues Pull Requests Packages Projects Releases Wiki Activity

OBS-URL: https://build.opensuse.org/package/show/openSUSE:Factory/ant?expand=0&rev=22

Browse Source
This commit is contained in:
OBS User unknown 2009-07-24 10:01:57 +00:00 committed by Git OBS Bridge
parent 4bdd320a47
commit 928538fa62
3 changed files with 10 additions and 489 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
ant-antlr.changes
View File

@ -1,3 +1,8 @@
-------------------------------------------------------------------
Mon Jul 20 15:48:54 CEST 2009 - coolo@novell.com
- build against log4j-mini to avoid build cycle
-------------------------------------------------------------------
Wed Jun 17 10:23:50 CEST 2009 - mvyskocil@suse.cz

216
ant-antlr.spec
View File

@ -29,7 +29,7 @@ Name: ant-antlr
# This line is not a comment, please do not remove it!
#%(sh %{_sourcedir}/ant-antlr-prepare.sh %{_sourcedir} %{name})
Version: 1.7.1
Release: 4
Release: 6
%if %bootstrap
Summary: Optional antlr Tasks for Ant
%else
@ -105,33 +105,11 @@ BuildArch: noarch
BuildRoot: %{_tmppath}/%{name}-%{version}-build
Obsoletes: apache-ant
Provides: apache-ant
%if %bootstrap
%description
Apache Ant is a Java-based build tool. This package contains optional
antlr tasks for Apache Ant.
Apache Ant is a Java-based build tool. This package contains optional
antlr tasks for Apache Ant.
%else
%description
Apache Ant is a Java-based build tool. This package contains optional
antlr tasks for Apache Ant.
Apache Ant is a Java-based build tool. This package contains optional
antlr tasks for Apache Ant.
%endif
%if %bootstrap
%package -n ant-jmf
@ -317,7 +295,7 @@ Summary: Optional apache log4j tasks for ant
Group: Development/Tools/Building
Requires: ant = %(echo `rpm -q --queryformat '%{VERSION}' ant`)
Requires: log4j
BuildRequires: log4j
BuildRequires: log4j-mini
Provides: ant-apache-log4j = %{version}-%{release}
Provides: ant-jakarta-log4j = %{version}-%{release}
Obsoletes: ant-jakarta-log4j < %{version}-%{release}
@ -366,7 +344,7 @@ This package contains optional apache regexp tasks for Apache Ant.
%package -n ant-javamail
License: Other uncritical OpenSource License ; Common Development and Distribution License
License: Other uncritical OpenSource License ; Common Development and Distribution License
Summary: Optional javamail tasks for ant
Group: Development/Tools/Building
Requires: ant = %(echo `rpm -q --queryformat '%{VERSION}' ant`)
@ -894,191 +872,3 @@ rm -rf $RPM_BUILD_ROOT
%endif
%changelog
* Wed Jun 17 2009 mvyskocil@suse.cz
- do not use Release number in Requires of subpackages
* Sun May 03 2009 ro@suse.de
- do not assume release number for ant and ant-antlr are identical
* Tue Apr 28 2009 mvyskocil@suse.cz
- update to 1.7.1. Upstream changes (full list is in WHATSNEW):
* String resources only have properties single expanded. If you relied on
<string> 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.
* <java> 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
* Wed Oct 01 2008 mvyskocil@suse.cz
- use a antlr-bootstrap do avoid another cycle
* Wed Jul 16 2008 coolo@suse.de
- avoid another build cycle
* Wed May 07 2008 mvyskocil@suse.cz
- build using gcj, to allow a openjdk6 bootstrap
- change a source and a target level to 1.5 in build.xml
* Sun Feb 17 2008 coolo@suse.de
- fix changelog for build service
* Sun Jul 08 2007 dbornkessel@suse.de
- add links to jar files in /usr/share/ant/lib
* Fri Jul 06 2007 dbornkessel@suse.de
- 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.
* <classconstants> 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.
* <script> and <scriptdef> now set the current thread context.
* Unrestrict the dbvendor names in the websphere element of the ejbjar task.
Bugzilla Report 40475.
* <env> nested element in <java>, <exec> and others is now case-insensitive
for windows OS. Bugzilla Report 28874.
* Removed support for xalan1 completely. Users of Xalan1 for Ant builds will
have to stay at ant 1.6.5 or upgrade to xalan2.
* Use org.apache.log4j.Logger instead of org.apache.log4j.Category.
Category has been deprecated for ~2 years and has been removed from
the log4j code. Logger was introduced in log4j 1.2 so users of
log4j 1.1 and log4j 1.0 need to upgrade to a newer version of log4j.
Bugzilla Report 31951.
* build.sysclasspath now also affects the bootclasspath handling of
spawned Java VMs. If you set build.sysclasspath to anything other
than "ignore" (or leave it unset, since "ignore" is the default when
it comes to bootclasspath handling), then the bootclasspath of the
VM running Ant will be added to the bootclasspath you've specified.
* The <java fork="false"> now as per default installs a security manager
using the default permissions. This is now independent of the
failonerror attribute. Bugzilla report 33361.
* <signjar> now notices when the jar and signedjar are equal, and switches
to the same dependency logic as when signedjar is omitted. This may break
something that depended upon signing in this situation. However, since
invoking the JDK jarsigner program with -signedjar set to the source jar
actually crashes the JVM on our (Java1.5) systems, we don't think any
build files which actually worked will be affected by the change.
* <signjar> used to ignore a nested fileset when a jar was also provided as an
attribute, printing a warning message; now it signs files in the fileset.
* An improved method of handling timestamp granularity differences between
client and server was added to the <ftp> task. FTP servers typically
have HH:mm timestamps whereas local filesystems have HH:mm:ss timestamps.
Previously, this required tweaking with the timediffmillis attribute
which also was used to handle timezone differences. Now, there is a new
timestampgranularity attribute. The default value for get operations is 0
since the user has the more powerful preservelastmodified attribute to work
with. Since this is not available on put operations the default value
adds a minute to the server timestamp in order to account for this,
Scripts which previously used timediffmillis to do this compensation may
need to be rewritten. timediffmillis has now been deprecated.
* On Java1.5+, Ant automatically sets the system property
java.net.useSystemProxies to true, which gives it automatic use of the local
IE (Windows) or Gnome2 (Unix/Linux) proxy settings. This may break any build
file that somehow relied on content outside the firewall being unreachable:
use the -noproxy command-line option to disable this new feature.
Note that the Java1.5 proxy configuration system still does not
appear to work reliably on Windows or Linux.
* Support for the XSL:P XML parser has been removed.
Bugzilla Report 23455.
* Visual Age for Java optional tasks removed.
* Testlet (test) optional task removed.
* Icontract optional task removed.
* Metamata (maudit, mmetrics, and mparse tasks) removed.
* Sitraka (jpcoverage, jpcovmerge, jpcovreport) tasks suppressed.
* <fixcrlf> used \r (Mac) line endings on OS X, whose proper line separator
is \n (Unix). Bugzilla report 39585.
* <scp> now optionally supports the sftp protocol, you may need a
newer jsch.jar. Bugzilla Report 39373.
* Ant launcher program prints errors to stderr, and exits with a 2 exit code
value if, for any reason, it cannot actually start Ant proper. This will only
affect programs/scripts that called the launcher and which did not want to
receive an error if Ant itself would not start
* All .NET tasks are now deprecated in favor of the new .NET Antlib:
http://ant.apache.org/antlibs/dotnet/index.html
* Tue May 08 2007 dbornkessel@suse.de
- removed all jai stuff as jai was dropped
* Fri Sep 22 2006 dbornkessel@suse.de
- added source=1.4
* Mon May 08 2006 dbornkessel@suse.de
- changed last change (see line below): Requires are only bound to the version, not to the release anymore
--> lrupp: fix Requires for ant (#171473 describes the same for dbus-1)
* Thu Feb 02 2006 dbornkessel@suse.de
* Thu Feb 02 2006 dbornkessel@suse.de
- fixed rpmlint errors and warnings
- fixed rpmlint errors and warnings
* Thu Feb 02 2006 dbornkessel@suse.de
- fixed rpmlint errors and warnings
* Tue Jan 31 2006 dbornkessel@suse.de
- only ant-antlr updates
- only ant-antlr updates
* Tue Jan 31 2006 dbornkessel@suse.de
- removed noarch due to different dependencies
- removed jsch and commons-net because we don't have the necessary packages
- ifarch'ed jai as it has a binary only dependency on a i386-only package
* Fri Jan 27 2006 dbornkessel@suse.de
- added four missing xsl files
- removed JAVA_HOME magic
- added four missing xsl files
- removed JAVA_HOME magic
- added BuildRoot
- removed JAVA_HOME magic
* Wed Jan 25 2006 dbornkessel@suse.de
- build optional task in an extra spec file due to circular dependencies
* Tue Jan 24 2006 dbornkessel@suse.de
- Not dependend on xml-commons-apis, which are provided by xerces-j2, which does not
depend on ant package (in contrast to old dependency on
xml-commons-apis <-> ant)
- optional task are now again in extra spec file ant-antlr
- Not dependend on xml-commons-apis, which are provided by xerces-j2, which does not
depend on ant package (in contrast to old dependency on
xml-commons-apis <-> ant)
- optional task are now again in extra spec file ant-antlr
* Thu Jan 19 2006 dbornkessel@suse.de
- Integrated ant and ant-antlr again in one spec file as there is no
dependency loop ... jpackage BuildRequires were wrong.
- updated to version 1.6.5
- Integrated ant and ant-antlr again in one spec file as there is no
dependency loop ... jpackage BuildRequires were wrong.
- updated to version 1.6.5
* Mon Dec 19 2005 dbornkessel@suse.de
- added if statement that hinders unwanted creation of a file within a for loop
- added if statement that hinders unwanted creation of a file within a for loop
* Thu Sep 29 2005 dmueller@suse.de
- add norootforbuild
- add norootforbuild
* Fri Mar 04 2005 skh@suse.de
- rely on jpackage-utils' java-functions to set JAVA_HOME correctly
- rely on jpackage-utils' java-functions to set JAVA_HOME correctly
* Sun Sep 05 2004 skh@suse.de
- create and add /usr/share/java/ant to file list for optional
tasks to put their jars into
* Thu Sep 02 2004 skh@suse.de
- renamed from apache-ant to ant
- switched to JPackage 1.5 version
- updated to version 1.6.2
- split off optional tasks into separate package to solve build
dependency loop in JPackage

278
ant.spec
View File

@ -28,7 +28,7 @@ Name: ant
# This line is not a comment, please do not remove it!
#%(sh %{_sourcedir}/ant-antlr-prepare.sh %{_sourcedir} %{name})
Version: 1.7.1
Release: 4
Release: 6
%if %bootstrap
Summary: A Java-Based Build Tool
%else
@ -104,7 +104,6 @@ BuildArch: noarch
BuildRoot: %{_tmppath}/%{name}-%{version}-build
Obsoletes: apache-ant
Provides: apache-ant
%if %bootstrap
%description
Apache Ant is a Java-based build tool. In theory, it is kind of like
@ -141,116 +140,6 @@ Ant has an <exec> task that allows different commands to be executed
based on the OS used.
Apache Ant is a Java-based build tool. In theory, it is kind of like
Make, but without Make's wrinkles.
Why another build tool when there is already make, gnumake, nmake, jam,
and others? Because all those tools have limitations that Ant's
original author could not live with when developing software across
multiple platforms. Make-like tools are inherently shell-based--they
evaluate a set of dependencies then execute commands, not unlike what
you would issue in a shell. This means that you can easily extend these
tools by using or writing any program for the OS that you are working
on. However, this also means that you limit yourself to the OS, or at
least the OS type, such as Unix, that you are working on.
Makefiles are inherently evil as well. Anybody who has worked on them
for any time has run into the dreaded tab problem. "Is my command not
executing because I have a space in front of my tab???" said the
original author of Ant way too many times. Tools like Jam took care of
this to a great degree, but still have yet another format to use and
remember.
Ant is different. Instead of a model where it is extended with
shell-based commands, Ant is extended using Java classes. Instead of
writing shell commands, the configuration files are XML-based, calling
out a target tree where various tasks are executed. Each task is run by
an object that implements a particular task interface.
Granted, this removes some of the expressive power that is inherent by
being able to construct a shell command such as `find . -name foo -exec
rm {}`, but it gives you the ability to be cross-platform--to work
anywhere and everywhere. If you really need to execute a shell command,
Ant has an <exec> task that allows different commands to be executed
based on the OS used.
%else
%description
Apache Ant is a Java-based build tool. In theory, it is kind of like
Make, but without Make's wrinkles.
Why another build tool when there is already make, gnumake, nmake, jam,
and others? Because all those tools have limitations that Ant's
original author could not live with when developing software across
multiple platforms. Make-like tools are inherently shell-based--they
evaluate a set of dependencies then execute commands, not unlike what
you would issue in a shell. This means that you can easily extend these
tools by using or writing any program for the OS that you are working
on. However, this also means that you limit yourself to the OS, or at
least the OS type, such as Unix, that you are working on.
Makefiles are inherently evil as well. Anybody who has worked on them
for any time has run into the dreaded tab problem. "Is my command not
executing because I have a space in front of my tab???" said the
original author of Ant way too many times. Tools like Jam took care of
this to a great degree, but still have yet another format to use and
remember.
Ant is different. Instead of a model where it is extended with
shell-based commands, Ant is extended using Java classes. Instead of
writing shell commands, the configuration files are XML-based, calling
out a target tree where various tasks are executed. Each task is run by
an object that implements a particular task interface.
Granted, this removes some of the expressive power that is inherent by
being able to construct a shell command such as `find . -name foo -exec
rm {}`, but it gives you the ability to be cross-platform--to work
anywhere and everywhere. If you really need to execute a shell command,
Ant has an <exec> task that allows different commands to be executed
based on the OS used.
Apache Ant is a Java-based build tool. In theory, it is kind of like
Make, but without Make's wrinkles.
Why another build tool when there is already make, gnumake, nmake, jam,
and others? Because all those tools have limitations that Ant's
original author could not live with when developing software across
multiple platforms. Make-like tools are inherently shell-based--they
evaluate a set of dependencies then execute commands, not unlike what
you would issue in a shell. This means that you can easily extend these
tools by using or writing any program for the OS that you are working
on. However, this also means that you limit yourself to the OS, or at
least the OS type, such as Unix, that you are working on.
Makefiles are inherently evil as well. Anybody who has worked on them
for any time has run into the dreaded tab problem. "Is my command not
executing because I have a space in front of my tab???" said the
original author of Ant way too many times. Tools like Jam took care of
this to a great degree, but still have yet another format to use and
remember.
Ant is different. Instead of a model where it is extended with
shell-based commands, Ant is extended using Java classes. Instead of
writing shell commands, the configuration files are XML-based, calling
out a target tree where various tasks are executed. Each task is run by
an object that implements a particular task interface.
Granted, this removes some of the expressive power that is inherent by
being able to construct a shell command such as `find . -name foo -exec
rm {}`, but it gives you the ability to be cross-platform--to work
anywhere and everywhere. If you really need to execute a shell command,
Ant has an <exec> task that allows different commands to be executed
based on the OS used.
%endif
%if %bootstrap
%package -n ant-jmf
@ -485,7 +374,7 @@ This package contains optional apache regexp tasks for Apache Ant.
%package -n ant-javamail
License: Other uncritical OpenSource License ; Common Development and Distribution License
License: Other uncritical OpenSource License ; Common Development and Distribution License
Summary: Optional javamail tasks for ant
Group: Development/Tools/Building
Requires: ant = %(echo `rpm -q --queryformat '%{VERSION}' ant`)
@ -1013,166 +902,3 @@ rm -rf $RPM_BUILD_ROOT
%endif
%changelog
* Wed Jun 17 2009 mvyskocil@suse.cz
- do not use Release number in Requires of subpackages
* Sun May 03 2009 ro@suse.de
- do not assume release number for ant and ant-antlr are identical
* Tue Apr 28 2009 mvyskocil@suse.cz
- update to 1.7.1. Upstream changes (full list is in WHATSNEW):
* String resources only have properties single expanded. If you relied on
<string> 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.
* <java> 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
* Mon Nov 03 2008 mvyskocil@suse.cz
- [bnc#440645] - ant fails without installed jdk:
- added a java-devel to Recommends:
* Mon Jul 21 2008 ro@suse.de
- use xerces-j2-bootstrap to build (as early as possible)
- add java doc dir to filelist of javadoc subpackage to fix build
* Wed Jul 16 2008 coolo@suse.de
- avoid another build cycle
* Wed May 07 2008 mvyskocil@suse.cz
- build using gcj, to allow a openjdk6 bootstrap
- change a source and a target level to 1.5 in build.xml
* Tue Aug 14 2007 skh@suse.de
- disable junit tests and remove junit from BuildRequires to break
circular build dependency
* Fri Jul 06 2007 dbornkessel@suse.de
- 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.
* <classconstants> 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.
* <script> and <scriptdef> now set the current thread context.
* Unrestrict the dbvendor names in the websphere element of the ejbjar task.
Bugzilla Report 40475.
* <env> nested element in <java>, <exec> and others is now case-insensitive
for windows OS. Bugzilla Report 28874.
* Removed support for xalan1 completely. Users of Xalan1 for Ant builds will
have to stay at ant 1.6.5 or upgrade to xalan2.
* Use org.apache.log4j.Logger instead of org.apache.log4j.Category.
Category has been deprecated for ~2 years and has been removed from
the log4j code. Logger was introduced in log4j 1.2 so users of
log4j 1.1 and log4j 1.0 need to upgrade to a newer version of log4j.
Bugzilla Report 31951.
* build.sysclasspath now also affects the bootclasspath handling of
spawned Java VMs. If you set build.sysclasspath to anything other
than "ignore" (or leave it unset, since "ignore" is the default when
it comes to bootclasspath handling), then the bootclasspath of the
VM running Ant will be added to the bootclasspath you've specified.
* The <java fork="false"> now as per default installs a security manager
using the default permissions. This is now independent of the
failonerror attribute. Bugzilla report 33361.
* <signjar> now notices when the jar and signedjar are equal, and switches
to the same dependency logic as when signedjar is omitted. This may break
something that depended upon signing in this situation. However, since
invoking the JDK jarsigner program with -signedjar set to the source jar
actually crashes the JVM on our (Java1.5) systems, we don't think any
build files which actually worked will be affected by the change.
* <signjar> used to ignore a nested fileset when a jar was also provided as an
attribute, printing a warning message; now it signs files in the fileset.
* An improved method of handling timestamp granularity differences between
client and server was added to the <ftp> task. FTP servers typically
have HH:mm timestamps whereas local filesystems have HH:mm:ss timestamps.
Previously, this required tweaking with the timediffmillis attribute
which also was used to handle timezone differences. Now, there is a new
timestampgranularity attribute. The default value for get operations is 0
since the user has the more powerful preservelastmodified attribute to work
with. Since this is not available on put operations the default value
adds a minute to the server timestamp in order to account for this,
Scripts which previously used timediffmillis to do this compensation may
need to be rewritten. timediffmillis has now been deprecated.
* On Java1.5+, Ant automatically sets the system property
java.net.useSystemProxies to true, which gives it automatic use of the local
IE (Windows) or Gnome2 (Unix/Linux) proxy settings. This may break any build
file that somehow relied on content outside the firewall being unreachable:
use the -noproxy command-line option to disable this new feature.
Note that the Java1.5 proxy configuration system still does not
appear to work reliably on Windows or Linux.
* Support for the XSL:P XML parser has been removed.
Bugzilla Report 23455.
* Visual Age for Java optional tasks removed.
* Testlet (test) optional task removed.
* Icontract optional task removed.
* Metamata (maudit, mmetrics, and mparse tasks) removed.
* Sitraka (jpcoverage, jpcovmerge, jpcovreport) tasks suppressed.
* <fixcrlf> used \r (Mac) line endings on OS X, whose proper line separator
is \n (Unix). Bugzilla report 39585.
* <scp> now optionally supports the sftp protocol, you may need a
newer jsch.jar. Bugzilla Report 39373.
* Ant launcher program prints errors to stderr, and exits with a 2 exit code
value if, for any reason, it cannot actually start Ant proper. This will only
affect programs/scripts that called the launcher and which did not want to
receive an error if Ant itself would not start
* All .NET tasks are now deprecated in favor of the new .NET Antlib:
http://ant.apache.org/antlibs/dotnet/index.html
* Fri Sep 22 2006 dbornkessel@suse.de
- read in properties in /etc/ant.conf
- added source=1.4
* Mon May 08 2006 dbornkessel@suse.de
- only ant-antlr updates
* Thu Feb 02 2006 dbornkessel@suse.de
- fixed rpmlint errors and warnings
* Tue Jan 31 2006 dbornkessel@suse.de
- only ant-antlr updates
* Fri Jan 27 2006 dbornkessel@suse.de
- added four missing xsl files
- removed JAVA_HOME magic
* Tue Jan 24 2006 dbornkessel@suse.de
- Not dependend on xml-commons-apis, which are provided by xerces-j2, which does not
depend on ant package (in contrast to old dependency on
xml-commons-apis <-> ant)
- optional task are now again in extra spec file ant-antlr
* Thu Jan 19 2006 dbornkessel@suse.de
- Integrated ant and ant-antlr again in one spec file as there is no
dependency loop ... jpackage BuildRequires were wrong.
- updated to version 1.6.5
* Mon Dec 19 2005 dbornkessel@suse.de
- added if statement that hinders unwanted creation of a file within a for loop
* Thu Sep 29 2005 dmueller@suse.de
- add norootforbuild
* Fri Mar 04 2005 skh@suse.de
- rely on jpackage-utils' java-functions to set JAVA_HOME correctly
* Sun Sep 05 2004 skh@suse.de
- create and add /usr/share/java/ant to file list for optional
tasks to put their jars into
* Thu Sep 02 2004 skh@suse.de
- renamed from apache-ant to ant
- switched to JPackage 1.5 version
- updated to version 1.6.2
- split off optional tasks into separate package to solve build
dependency loop in JPackage