place. The tar-task used another constructor. Simply copied the verification
to the other constructor to do the check there also. Now throws a
RuntimeException.
Submitted By: "Nico Seessle" <Nico.Seessle@epost.de>
git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@268494 13f79535-47bb-0310-9956-ffa450edef68
The example for exec does now work on Windows.
Added a note thet NetComponents needs to be downloaded from
www.savarese.org.
Submitted By: "Nico Seessle" <Nico.Seessle@epost.de>
git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@268491 13f79535-47bb-0310-9956-ffa450edef68
You can add support classes to all the generated jar fils by including a
<support-classes> nested element. This is effectively a fileset and
includes the ability to reference another fileset by refid
So
<ejbjar ...>
<support-classes dir="${build.classes.server}">
<include name="**/*.class"/>
</support-classes>
...
</ejbjar>
or
<ejbjar ...>
<support-classes refid="support.fileset"/>
...
</ejbjar>
Please note the following.
==========================
If your ejbjar task generates multiple jar files, the support classes will be
added to each one.
The nested element name may change. I am using it to test a facility I added
to the core. If it does change, it will change to <support>
git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@268486 13f79535-47bb-0310-9956-ffa450edef68
through a createElement(String elementName) factory method. This has two
applications.
It allows a task to define what nested elements are supported
dynamically, perhaps through a configuration file. This is useful
for tasks that support a plug-in architecture, as I am trying to
achieve with <ejbjar>
As a byproduct, it also allows a task to support nested elements which
cannot be mapped to valid Java method names, such as <support-classes>. The
use of hyphenated compound names is relatively common style in XML DTDs
git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@268485 13f79535-47bb-0310-9956-ffa450edef68
on the classpath, a class it depends on is not. As this code is currently catching
ClassNotFound exceptions anyway, this is not a major change. It will log a
warning.
git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@268484 13f79535-47bb-0310-9956-ffa450edef68
---
With these patches, Zip (and derivative tasks such as Jar and War) can
merge the entries of multiple zip files into a single output zip file.
The contents of an input zip file may be selectively extracted based on
include/exclude patterns.
An included zip file is specified using a <fileset> with a "src" attribute,
as in:
<target name="jartest">
<jar jarfile="utils.jar">
<fileset
src="weblogic.jar"
includes="weblogic/utils/"
excludes="weblogic/utils/jars/,**/reflect/"
/>
</jar>
</target>
In this example, a subset of the "weblogic/utils" directory is extracted
from weblogic.jar, into utils.jar.
The fileset may also contain "prefix" and "fullpath" attributes (the
functionality of PrefixedFileSet has been retained in the new class
ZipFileSet). Prefixes apply to directory-based and zip-based filesets.
The fullpath attributes applies only to a single file in a directory-based
fileset.
The War task may extract entries from a zip file for all of its filesets
(including the files in "classes" and "lib").
The motivation for this change is:
1) There is significant overlap between "jlink" and "zip", and it seemed
better to combine them.
2) "jlink" does not support include/exclude patterns which are extremely
useful for writing packaging-type tasks such as Zip/Jar/War. This
was my main motivation.
3) By adding this functionality to the base task, it can also be used in
derivative tasks such as Jar and War.
---
Submitted By: Don Ferguson <don@bea.com>
git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@268459 13f79535-47bb-0310-9956-ffa450edef68
---
With these patches, Zip (and derivative tasks such as Jar and War) can
merge the entries of multiple zip files into a single output zip file.
The contents of an input zip file may be selectively extracted based on
include/exclude patterns.
An included zip file is specified using a <fileset> with a "src" attribute,
as in:
<target name="jartest">
<jar jarfile="utils.jar">
<fileset
src="weblogic.jar"
includes="weblogic/utils/"
excludes="weblogic/utils/jars/,**/reflect/"
/>
</jar>
</target>
In this example, a subset of the "weblogic/utils" directory is extracted
from weblogic.jar, into utils.jar.
The fileset may also contain "prefix" and "fullpath" attributes (the
functionality of PrefixedFileSet has been retained in the new class
ZipFileSet). Prefixes apply to directory-based and zip-based filesets.
The fullpath attributes applies only to a single file in a directory-based
fileset.
The War task may extract entries from a zip file for all of its filesets
(including the files in "classes" and "lib").
The motivation for this change is:
1) There is significant overlap between "jlink" and "zip", and it seemed
better to combine them.
2) "jlink" does not support include/exclude patterns which are extremely
useful for writing packaging-type tasks such as Zip/Jar/War. This
was my main motivation.
3) By adding this functionality to the base task, it can also be used in
derivative tasks such as Jar and War.
---
Submitted By: Don Ferguson <don@bea.com>
git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@268458 13f79535-47bb-0310-9956-ffa450edef68
These should be moved to a contribution project
when one is created.
Submitted by: Wolf Siberski
Christoph Wilhelms
git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@268446 13f79535-47bb-0310-9956-ffa450edef68
Peter Donald
Conor MacNeill
Stefan Bodewig
Jon Scott Stevens
metasim
Diane Holt
glennm