control over the command line. If no element has been specified, the
names for the source files will be put at the end.
git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@268220 13f79535-47bb-0310-9956-ffa450edef68
any args, which must be at the front of the JVM arguments, can be specified.
This is specifically to support the -server option of the JVM under Unix.
Reported by: Cyril Bouteille <CyrilBouteille@yahoo.com>
git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@268214 13f79535-47bb-0310-9956-ffa450edef68
message more suitable for ant end-users rather than ant developers.
Submitted by: Erik Meade <emeade@geekfarm.org>
git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@268213 13f79535-47bb-0310-9956-ffa450edef68
So, when writing the .ser file, it will be placed into the same relative
directory in which the source .txt file is found in the descriptor hierarchy.
Similary the .ser files will have the correct manifest entires in the generated
manifest file.
git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@268211 13f79535-47bb-0310-9956-ffa450edef68
defaults to false.
To keep genrated code, use the keepgenerated="true"
Submitted by: William Turnbull <William.Turnbull@trcinc.com>
git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@268208 13f79535-47bb-0310-9956-ffa450edef68
Also introduced logging levels to provide finer control over
when messages are writen out. The levels simply reflect the
current Project.MSG_* values.
Suggested by: Wolf Siberski
git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@268204 13f79535-47bb-0310-9956-ffa450edef68
This adds a lot of power to copy and move, we can drop the optional
RenameExt task for example as
<renamext srcdir="src" destdir="dest" fromextension=".java.keep"
toextension=".java" replace="true" />
can now be written as
<move todir="dest" overwrite="true">
<fileset dir="src" />
<mapper type="glob" from="*.java.keep" to="*.java" />
</move>
but more difficult transformations can be done as well.
git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@268203 13f79535-47bb-0310-9956-ffa450edef68
what I want to accomplish.
All tasks using a scanDir method to find the source files that are
newer than there targets should get a similar treatment as <copy>.
The major benefit is not to have the functionality in one place but
the added flexibility you get, when you allow the user to specify a
custom FileNameMapper to a task (not there yet).
Nothing (especially not the names) is carved into stone of course.
git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@268190 13f79535-47bb-0310-9956-ffa450edef68
on parsing the weblogic descriptor rather than using the naming convention. To
access the new behaviour set oldCMP="false" in the weblogic element.
This should allow the ejbjar task to support jars with more than one CMP bean
Submitted by: gayre <greg.ayre@destiny.com>
Some minor changes to Main.java - layout and wording.
git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@268186 13f79535-47bb-0310-9956-ffa450edef68
1) added an echo attribute to write to suppress output
2) added a timeout mechanism on reads
3) can now send an initial newline before expecting anything from the server
Submitted by: Scott Carlson <ScottCarlson@email.com>
git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@268179 13f79535-47bb-0310-9956-ffa450edef68
1. Change EJBJar so that super classes and super interfaces are included in
bean jar file. For this to work, the classpath can be specified at the
ejbjar level. This will be used for the weblogic nested element if it
is specified. If a classpath is also provided on the weblogic
nested element, it is concatenated with the task level classpath. Since
the processing is done in the nested element in any case, current usage
where the classpath is specified in the nested element is sufficient
for these checks to work.
2. Allow <classpath> nested elements to be used to specify the classpath. This can
be used for both the task level and nested element level classpaths.
3. Change the weblogic jar generation to run ejbc only if the interfaces have
changed. Changes to the bean classes will not cause ejbc to run. This behaviour
must be enabled by setting the attribute rebuild="false" in the weblogic
element.
Submitted by: Brian Towles <brian@towles.com>
git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@268173 13f79535-47bb-0310-9956-ffa450edef68
Stefan Bodewig
metasim
Peter Donald
Conor MacNeill
glennm