svn commit: r468568 - in /ant/core/trunk: WHATSNEW docs/manual/CoreTasks/war.html src/main/org/apache/tools/ant/taskdefs/War.java src/tests/antunit/taskdefs/war-test.xml

[stevel]

Author: stevel
Date: Fri Oct 27 15:33:42 2006
New Revision: 468568

URL: http://svn.apache.org/viewvc?view=rev&rev=468568
Log:
Made web.xml non optional again, as it was hiding too many bugs (e.g war files 
for tomcat 5), but added an attribute to make it optional. 

More tests, especially for updates. One test is disabled because it fails. The 
task fails if you are pulling in a web.xml on an existing web.xml file via a 
fileset if update=false, because the fileset version checking is hiding the 
inclusion of the web.xml file from the war task -its being dropped before we 
notice. This is not a BC problem. Maybe I should always make web.xml mandatory 
to stop this behavior arising.

Modified:
ant/core/trunk/WHATSNEW
ant/core/trunk/docs/manual/CoreTasks/war.html
ant/core/trunk/src/main/org/apache/tools/ant/taskdefs/War.java
ant/core/trunk/src/tests/antunit/taskdefs/war-test.xml

Modified: ant/core/trunk/WHATSNEW
URL: 
http://svn.apache.org/viewvc/ant/core/trunk/WHATSNEW?view=diff&rev=468568&r1=468567&r2=468568
==
--- ant/core/trunk/WHATSNEW (original)
+++ ant/core/trunk/WHATSNEW Fri Oct 27 15:33:42 2006
@@ -28,9 +28,8 @@
   Bugzilla 40019.
 
 *  task now allows you to omit the web.xml file. as this is optional
-  in the servlet 2.5 and Java EE 5 APIs. If you do want a web.xml file, it
-  can be pulled in by any nested fileset or resource reference; the webxml
-  attribute is optional.
+  in the servlet 2.5 and Java EE 5 APIs. set needxmlfile="false" to
+  avoid a missing web.xml file from halting the build.  
 
 * Diagnostics catches and logs security exceptions when accessing system 
properties.
 

Modified: ant/core/trunk/docs/manual/CoreTasks/war.html
URL: 
http://svn.apache.org/viewvc/ant/core/trunk/docs/manual/CoreTasks/war.html?view=diff&rev=468568&r1=468567&r2=468568
==
--- ant/core/trunk/docs/manual/CoreTasks/war.html (original)
+++ ant/core/trunk/docs/manual/CoreTasks/war.html Fri Oct 27 15:33:42 2006
@@ -41,14 +41,17 @@
 
 Before Servlet API 2.5/Java EE 5, a WEB-INF/web.xml file was mandatory in a
 WAR file, so this task failed if the webxml attribute was 
missing.
-As the web.xml file is now optional, the webxml attribute is 
now
-downgraded to being optional. The task will warn if the file is not
-included as an attribute or in a fileset, but still succeed. The task
-will also complain if more than one web.xml file is added to the JAR. 
+As the web.xml file is now optional, the webxml attribute may 
now
+be made optional. However, as most real web applications do need a web.xml 
file,
+it is not optional by default. The task will fail if the file is not
+included, unless the needxmlfile attribute
+is set to true. The task
+will warn if more than one web.xml file is added to the JAR  
+through the filesets.
 
 
 
-Please note that the zip format allows multiple files of the same
+Please note that the Zip format allows multiple files of the same
 fully-qualified name to exist within a single archive.  This has been
 documented as causing various problems for unsuspecting users.  If you wish
 to avoid this behavior you must set the duplicate attribute
@@ -73,8 +76,18 @@
   
   
 webxml
-The deployment descriptor to use (WEB-INF/web.xml).
-No (since Ant1.7)
+The servlet configuration descriptor to use 
(WEB-INF/web.xml).
+Yes, unless needxmlfile is true,
+the file is pulled in via a nested fileset, or an existing WAR file is
+being updated.
+  
+  
+needxmlfile
+Flag to indicate whether or not the web.xml file is 
needed.
+I=it should be set to false when generating
+servlet 2.5+ WAR files without a web.xml file.
+Since Ant 1.7
+No -default "true"
   
   
 basedir

Modified: ant/core/trunk/src/main/org/apache/tools/ant/taskdefs/War.java
URL: 
http://svn.apache.org/viewvc/ant/core/trunk/src/main/org/apache/tools/ant/taskdefs/War.java?view=diff&rev=468568&r1=468567&r2=468568
==
--- ant/core/trunk/src/main/org/apache/tools/ant/taskdefs/War.java (original)
+++ ant/core/trunk/src/main/org/apache/tools/ant/taskdefs/War.java Fri Oct 27 
15:33:42 2006
@@ -55,11 +55,15 @@
 /**
  * flag set if the descriptor is added
  */
-private boolean descriptorAdded;
+private boolean needxmlfile=true;
 private File addedWebXmlFile;
 
 private static final FileUtils FILE_UTILS = FileUtils.getFileUtils();
-private static final String XML_DESCRIPTOR_PATH = "web-inf/web.xml";
+/** path to web.xml file */
+private static final String XML_DESCRIPTOR_PATH = "WEB-INF/web.xml";
+/** lower case version for comparisons */
+private static final String XML_DESCRIPTOR_PATH_LC =
+XML_DESCRIPTOR_PATH.toLowerCase(Locale.

Re: Ideas on support of javax.script'ing

[Paul King]

Peter Reilly wrote:

On 10/27/06, Paul King <[EMAIL PROTECTED]> wrote:

Peter Reilly wrote:
> [...] however, having bsf.jar and js.jar in
> the $ANT_HOME/lib, is a user's choice, so if they are there it is
> a good assumption that the user wants to use them.

I think that Groovy has native jsr support but jruby didn't last
time I checked (though that may soon or may have already changed)


Support for jruby is provided via the
java scripting project:
https://scripting.dev.java.net/
They have a number of engines for various languages
that do not have native implementations.
(provided as language engine jar files).

Peter


Cool. I didn't remember the list being so complete last time
I looked. I guess the question still remains. If I needed BSF
for e.g. NetRexx would I want BSF or JSR for everything else?
I suspect I would be going JSR if I could.

Paul.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

svn commit: r468556 - /ant/core/trunk/src/main/org/apache/tools/ant/filters/TokenFilter.java

[stevel]

Author: stevel
Date: Fri Oct 27 15:08:51 2006
New Revision: 468556

URL: http://svn.apache.org/viewvc?view=rev&rev=468556
Log:
remove some imports we dont need

Modified:
ant/core/trunk/src/main/org/apache/tools/ant/filters/TokenFilter.java

Modified: ant/core/trunk/src/main/org/apache/tools/ant/filters/TokenFilter.java
URL: 
http://svn.apache.org/viewvc/ant/core/trunk/src/main/org/apache/tools/ant/filters/TokenFilter.java?view=diff&rev=468556&r1=468555&r2=468556
==
--- ant/core/trunk/src/main/org/apache/tools/ant/filters/TokenFilter.java 
(original)
+++ ant/core/trunk/src/main/org/apache/tools/ant/filters/TokenFilter.java Fri 
Oct 27 15:08:51 2006
@@ -25,11 +25,8 @@
 import org.apache.tools.ant.ProjectComponent;
 import org.apache.tools.ant.types.RegularExpression;
 import org.apache.tools.ant.types.Substitution;
-import org.apache.tools.ant.util.FileUtils;
 import org.apache.tools.ant.util.Tokenizer;
-import org.apache.tools.ant.util.FileTokenizer;
 import org.apache.tools.ant.util.LineTokenizer;
-import org.apache.tools.ant.util.StringTokenizer;
 import org.apache.tools.ant.util.StringUtils;
 import org.apache.tools.ant.util.regexp.Regexp;
 



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Ideas on support of javax.script'ing

[Peter Reilly]

On 10/27/06, Paul King <[EMAIL PROTECTED]> wrote:

Peter Reilly wrote:
> [...] however, having bsf.jar and js.jar in
> the $ANT_HOME/lib, is a user's choice, so if they are there it is
> a good assumption that the user wants to use them.

I think that Groovy has native jsr support but jruby didn't last
time I checked (though that may soon or may have already changed)


Support for jruby is provided via the
java scripting project:
https://scripting.dev.java.net/
They have a number of engines for various languages
that do not have native implementations.
(provided as language engine jar files).

Peter


so I might want to go with native jsr when using Groovy even
though I have bsf.jar in my classpath for when I want to
use jruby. So, the 'bsf:', 'jsr:' switch sounds good to me.

Paul.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Ideas on support of javax.scripting

[Jesse Glick]

Peter Reilly wrote:
The idea is that ant-core code would first check for the language 
implementation in bsf and if that (the language or bsf) does not 
exist, ant-core will then check for javax.script support for the

language.


+1

-J.

--
[EMAIL PROTECTED]  x22801  netbeans.org  ant.apache.org
  http://google.com/search?q=e%5E%28pi*i%29%2B1


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Ideas on support of javax.script'ing

[Paul King]

Peter Reilly wrote:

[...] however, having bsf.jar and js.jar in
the $ANT_HOME/lib, is a user's choice, so if they are there it is
a good assumption that the user wants to use them.


I think that Groovy has native jsr support but jruby didn't last
time I checked (though that may soon or may have already changed)
so I might want to go with native jsr when using Groovy even
though I have bsf.jar in my classpath for when I want to
use jruby. So, the 'bsf:', 'jsr:' switch sounds good to me.

Paul.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Ideas on support of javax.script'ing

[Peter Reilly]

On 10/27/06, Dominique Devienne <[EMAIL PROTECTED]> wrote:

On 10/27/06, Peter Reilly <[EMAIL PROTECTED]> wrote:
> I have been thinking on how to support javax.script in future
> versions of ant.
>
> Initially, I though of using a new task  or something
> similar, but have reconsidered and now think that the same
> tasks (

Re: Redirector vs. getProject().setProperty(

[Matt Benson]

"editing a task?" Do you mean writing your own?  It
depends on what you want to do.  Redirectors were
created to (1) make it possible to declare the I/O
handling of your task separately from the task itself
(they are ref/reusable); and (2) specifically to allow
mapped output destinations in the case of e.g.
.

-Matt

--- Hunter Peress <[EMAIL PROTECTED]> wrote:

> when editing a task is there any reason to set an
> output property using the
> redirector
> vs. getProject().setProperty() ??
> 


__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Ideas on support of javax.script'ing

[Dominique Devienne]

On 10/27/06, Peter Reilly <[EMAIL PROTECTED]> wrote:

I have been thinking on how to support javax.script in future
versions of ant.

Initially, I though of using a new task  or something
similar, but have reconsidered and now think that the same
tasks (

Ideas on support of javax.script'ing

[Peter Reilly]

I have been thinking on how to support javax.script in future
versions of ant.

Initially, I though of using a new task  or something
similar, but have reconsidered and now think that the same
tasks (

AW: A note on release votes

[Jan.Materne]

>I think that - apart from writing the script which could be 
>done with the technology we already know - the thing that 
>would hold us from doing it in the case of ant is that you 
>would not put on a "release.apache.org" server our non open 
>source dependencies such as weblogic and starteam because we 
>do not know if this would create legal problems.

Do the ASF have the possibility of holding the "release.apache.org"
private?
Maybe a VMware instance and the full-automated-release-build could also
do the
start/stop of that VMware instance which holds the running servers and
libraries
(included into the build by a) copying via ssh into the build
environment or
b) mounted into the build environment via Samba/NFS/???).


Jan

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [RE-VOTE] AntUnit 1.0 Beta 2

[Dominique Devienne]

I've re-built AntUnit with -source 1.2 and uploaded everything to
.  I'd like to release
those files as 1.0Beta2.


+1. --DD

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: A note on release votes

[Antoine Levy-Lambert]

Stefan Bodewig wrote:
> Hi all,
>
> in the past we have been a bit lax on releases.  We've beasically been
> voting on the source tree (yes, you can build a release on Sunday) and
> not on the files being released.  Now that we are sponsoring an
> Incubator podling, we might better be a bit more strict so that the
> Ivy community doesn't pick up our bad habits 8-)
>
> Formally we don't even need a release plan, everybody can build
> distribution files and start a release vote at any time, but I think
> we should stick with our current procedure.
>
> The second part is that after the distribution has been built, we must
> vote on those distribution files before they are published.
>   
Hello Stefan,

I prefer the procedure which I have used for Ant 1.6 and for the betas
of 1.7 to define a release date in the vote thread,
and then to build and publish the release "mechanically" on the release
date.

Voting on the source tree seems for me the right thing to do. We should
automate the generation and the upload of the distribution as much as
possible so that
there is no leeway for the release manager to tweak the artifacts.

Ideally, the releases should be built fully automatically by a
server/script/program. It is quite easy to think how this would work.
For instance you would check in in a special directory a file
called release-ant-1.7.0.xml containing the date/time when to start the
build (in UTC), the subject and the text of the email messages to
announce the release, some pointers to generate the RELEASE-NOTES.html from
WHATSNEW, ...

I think that - apart from writing the script which could be done with
the technology we already know - the thing that would hold us from doing
it in the case of ant is that you would not put on a
"release.apache.org" server our non open source dependencies such as
weblogic and starteam because we do not know if this would create legal
problems.

Regards,

Antoine

> Stefan
>   


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [RE-VOTE] AntUnit 1.0 Beta 2

[Antoine Levy-Lambert]

+1

Antoine

PS afterwards, we need to update the jar checked in under lib/optional
in ant-core. ;-)

Stefan Bodewig wrote:
> Hi,
>
> I've re-built AntUnit with -source 1.2 and uploaded everything to
> .  I'd like to release
> those files as 1.0Beta2.
>
> Stefan
>
>   


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

svn commit: r468362 - /ant/core/trunk/build.xml

[antoine]

Author: antoine
Date: Fri Oct 27 05:54:29 2006
New Revision: 468362

URL: http://svn.apache.org/viewvc?view=rev&rev=468362
Log:
the mavenish release directory has moved

Modified:
ant/core/trunk/build.xml

Modified: ant/core/trunk/build.xml
URL: 
http://svn.apache.org/viewvc/ant/core/trunk/build.xml?view=diff&rev=468362&r1=468361&r2=468362
==
--- ant/core/trunk/build.xml (original)
+++ ant/core/trunk/build.xml Fri Oct 27 05:54:29 2006
@@ -1360,7 +1360,7 @@
 
 
 
-
+
 
   Uploading Ant version ${project.version}
   to host ${ssh.host} as ${apache.user}



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: svn commit: r466627 - in /ant/core/trunk/src/etc/poms: ./ ant-antlr/ ant-apache-bcel/ ant-apache-bsf/ ant-apache-log4j/ ant-apache-oro/ ant-apache-regexp/ ant-apache-resolver/ ant-commons-logging/

[Steve Loughran]

Antoine Levy-Lambert wrote:
FYI, the maven-to-RDF conversion we are attempting will eventually index 
every .class in every jar to look for duplicates. If I save a hash of 
every class we can even do version auditing. Oh, people will fear our 
auditor program. Working name: repo-man :)


-steve


Interesting. You will catch the guys of org.foo who redistribute org.bar ...



That's right. Once you publish your artifacts, we will find your dirty 
secrets. And is that a bad thing? No, I think not.


My goal is to add leading-edge rules to what constitutes an "acceptable" 
package. That means dependency validation, but it will also mean package 
introspection, warning at troublespots and other forms of artifact 
auditing.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [RE-VOTE] AntUnit 1.0 Beta 2

[Steve Loughran]

Stefan Bodewig wrote:

Hi,

I've re-built AntUnit with -source 1.2 and uploaded everything to
.  I'd like to release
those files as 1.0Beta2.




+1

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: FW: antunit branch for 1.6.x compatibility

[Steve Loughran]

Vladimir Egorov wrote:



-Original Message-
From: Steve Loughran [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 26, 2006 9:33 AM
To: Ant Developers List
Subject: Re: FW: antunit branch for 1.6.x compatibility

Vladimir Egorov wrote:

Sorry for a bit of a messy entry into the list. I did not realize

that

using html email could be a problem. Thanks Stephan for pointing

this

out.


My inquiry is in connection with TestLogic project on CodeShare.

Could you please expand a little on TestLogic for the rest of the

Ant

developers?

TestLogic is an initiative by BEA Systems Inc. Tools team to provide

an

open source testing framework for the enterprise. The flavor of this
effort is to provide the glue that would tie together existing
frameworks (e.g. JUnit) in a consistent manageable way. Over time,

we

want to cover the breadth of the enterprise testing needs, based on

our

knowledge of BEA Systems Inc. testing needs. The project is so far a
private project on CodeShare. We are planning to open source when we
reach some point of maturity and can get clearance, hopefully within

2-4

month.

That's interesting. Have you seen the work I'm doing with deployment

of

junit3/4/testng+other frameworks and merging of results


No we haven't seen your work. The 'merging of results' does sound like
the kind of thing we are doing; it would be interesting to learn more
from the links you kindly provided.


uniform serialization of results for over-RMI comms, and (b) some
evolving XML format. For (b) I've got marked up XHTML, but am thinking
of how to use Atom to integrate results, a polling app and log data:



http://smartfrog.org/presentations/distributed_testing_with_smartfrog_sl
id

es.pdf
http://video.google.co.uk/videosearch?q=smartfrog


We currently want to stay away from RMI as in our prior experience
framework RMI sometimes interferes with server RMI in unexpected ways.
Also we want to support non-java frameworks (e.g. WinRunner) via single
protocol.


We use RMI internally, but yes, we do want a wire protocol that is 
better long haul. One thing I'm thinking of for results is to publish 
stuff as Atom, but maybe also add a RESTy way of running Tests. I'd back 
this up with a servlet that could be deployed inside a web app/EAR, to 
do cactus-style running of tests inside an app server. I think cactus is 
wonderful, but dont see why you need to instantiate every test class 
inside the client-side machine, except for compatibility with legacy 
test runners.






Uniformity of both the java format and the xml output would be very
beneficial, and putting the stuff into antunit and  and



is part of my goal.


We are trying to with existing frameworks with minimum modifications.
For example, we support  by adding a custom nested 
(listener) that knows how to talk to us.


I was looking at tweaking that myself, but its complex because forked 
junit instantiates the listener in the remote process, where its hard to 
configure. With a cross-process run (in which the forked test run feeds 
results as serialized data or XML) you dont need that; the custom 
listener can live in ant's process.


If we come up with a new XML format, I'd just patch it in to , 
 and presumably, the junit4 task as and when I sit down to 
write it.


-steve

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: PermGen OutOfMemoryError in custom Iterator task, and ForEach - Suggestions Please

[Peter Reilly]

On 10/26/06, Robert Rice <[EMAIL PROTECTED]> wrote:

Peter,

Your suggestions were quite helpful.  The fix for me was to utilize a
post-ant1.7.0beta3 svn copy of ant.  I tested my Iterator-based task, as
well as  using the most recent svn ant.  In both cases, my builds
ran without OOME.  So it would seem that the memory leak squashing is paying
off.  Hopefully these will make it into the proposed beta4.

I do have a bonus, follow-up question.  Some of your dialog in the previous
post leads me to believe I am behind in ant-contrib knowledge.  I am using
ant-contrib-0.3, as made available through :
http://ant-contrib.sourceforge.net/.  While I realize that this is a rather
old build, I have found nothing newer.  In particular, your reference to
"Use antcontrib:[EMAIL PROTECTED] to reuse properties" leaves me a little
puzzled as I have not seen this construct or a reference to a  task.
Also, you had suggested to not use antcall.  The version of  that I
have uses antcall internally, which leaves me further confused.

There is a newer version of ant-contrib (version 1.0b2 from 2005.02.03)
on:
http://sourceforge.net/project/showfiles.php?group_id=36177
This is feached from:
http://ant-contrib.sourceforge.net/
using the downloads hyper-link.
The content on the page (http://ant-contrib.sourceforge.net/) needs updating
as it refers to ant-contrib0.3

There is a new task called  which uses ant1.6 macrodef internally,
the  task is still present - for use with ant1.5 and for bc purposes.

If you like, you can upload the svn version of ant-contrib, it includes
some fixes and some new http tasks.

Peter



Please point me in the correct direction, especially if there is
documentation available.

Thanks,
Robert Rice

On 10/24/06, Peter Reilly <[EMAIL PROTECTED]> wrote:
>
> On 10/23/06, Robert Rice <[EMAIL PROTECTED]> wrote:
> > I recently created a custom task that is an Iterator.  The goal of the
> task
> > is to accept a large date range ( like 3 years ) and split it into
> smaller
> > date ranges ( like 1 day at a time ).  I do a lot of work with date
> ranges.
> > Examples are running queries or fetching files that expect a time range.
> >
> > At each iteration, the task sets a couple of properties that represent
> the
> > limits of the smaller date range.  At this point, the task acts very
> much
> > like .  It requires one or more targets.  CallTaget tasks are
> > dynamically constructed for each target for each iteration.  They are
> then
> > executed.   The targets that are called are rather large themselves,
> > ultimately including about 10 targets or dependencies.
> >
> > The short is that I am running out of memory.  About 70 iterations in (
> > representing 70 days of work that has been accomplished ), I get an
> > OutOfMemoryError.  It looks something like:
> >
> > http-data:
> > [timer] Timer started.  Tasks started.
> > Exception in thread "Thread-72" java.lang.OutOfMemoryError: PermGen
> space
> > [timer] Timer interrupted. Tasks completed.
> >
> > And an example stacktrace:
> > Exception in thread "Thread-71"
> > /home/robert/dvl/java/bin/RetsDataCollector.xml:161: The following error
> > occurred while executing this
> > line:/home/robert/dvl/java/bin/RetsDataCollector.xml:127: Could not
> create
> > type mget due to java.lang.OutOfMemoryError: PermGen spaceat
> > org.apache.tools.ant.ProjectHelper.addLocationToBuildException(
> > ProjectHelper.java:539)
> > at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:384)
> > at org.apache.tools.ant.taskdefs.CallTarget.execute(
> CallTarget.java
> > :107)
> > at net.sf.antcontrib.logic.ForEach.execute(Unknown Source)
> > at org.apache.tools.ant.UnknownElement.execute(
> UnknownElement.java
> > :275)
> > at org.apache.tools.ant.Task.perform(Task.java:364)
> > at com.windermere.collector.task.Timer$TasksThread.run(Unknown
> > Source)
> > Caused by: /home/robert/dvl/java/bin/RetsDataCollector.xml:127: Could
> not
> > create type mget due to java.lang.OutOfMemoryError: PermGen
> spaceat
> > org.apache.tools.ant.AntTypeDefinition.createAndSet(
> AntTypeDefinition.java
> > :281)
> > at org.apache.tools.ant.AntTypeDefinition.icreate(
> > AntTypeDefinition.java:196)
> > at org.apache.tools.ant.AntTypeDefinition.create(
> > AntTypeDefinition.java:183)
> > at org.apache.tools.ant.ComponentHelper.createComponent(
> > ComponentHelper.java:199)
> > at org.apache.tools.ant.ComponentHelper.createComponent(
> > ComponentHelper.java:176)
> > at org.apache.tools.ant.UnknownElement.makeObject(
> > UnknownElement.java:388)
> > at org.apache.tools.ant.UnknownElement.maybeConfigure(
> > UnknownElement.java:158)
> > at org.apache.tools.ant.Task.perform(Task.java:363)
> > at org.apache.tools.ant.Target.execute(Target.java:341)
> > at org.apache.tools.ant.Target.performTasks(Target.java:369)
> > at org.apache.tools.ant.Project.execu

Re: svn commit: r468260 - /ant/antlibs/common/trunk/build.xml

[Peter Reilly]

On 10/27/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:

>Modified: ant/antlibs/common/trunk/build.xml
>
>+
>+
>+
>+


Stefan,
why do you have chosen the name "-source" (leading '-') instead of
"source"?

and not do it for "javac.debug" ?

Peter



Jan

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [RE-VOTE] AntUnit 1.0 Beta 2

[Peter Reilly]

+1 Peter

On 10/27/06, Stefan Bodewig <[EMAIL PROTECTED]> wrote:

Hi,

I've re-built AntUnit with -source 1.2 and uploaded everything to
.  I'd like to release
those files as 1.0Beta2.

Stefan

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

AW: svn commit: r468260 - /ant/antlibs/common/trunk/build.xml

[Jan.Materne]

>Modified: ant/antlibs/common/trunk/build.xml
> 
>+
>+
>+
>+


Stefan,
why do you have chosen the name "-source" (leading '-') instead of
"source"?

Jan

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: HelpStudioAnt (was: "AW: failure notice")

[Lars Monsees]

> Submitted (rev 468305). Should be online soon.

thx!


> 
> Would be good if you add some notes (and links) on your homepage
> about "HelpStudio" itself. I had never heard before 

Good idea, I´ll do that later.


Lars


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

AW: HelpStudioAnt (was: "AW: failure notice")

[Jan.Materne]

Submitted (rev 468305). Should be online soon.

Would be good if you add some notes (and links) on your homepage about 
"HelpStudio" itself.
I had never heard before 


Jan

>-Ursprüngliche Nachricht-
>Von: Lars Monsees [mailto:[EMAIL PROTECTED] 
>Gesendet: Donnerstag, 26. Oktober 2006 17:13
>An: 'Ant Developers List'
>Betreff: RE: HelpStudioAnt (was: "AW: failure notice")
>
>
>
> 4)
> Patching
> http://svn.apache.org/repos/asf/ant/core/trunk/xdocs/external.xml
> for the "External Tools and Tasks" page: I´m using Eclipse
> 3.1 on Windows.
> I know that I can create a patch to a file that is under 
> versioncontrol. Is there an easy way to create a patch besides 
> configuring the svn repository in Eclipse?
 
 You could also create the xml snippet ...
>>> 
>>> Already done. I thought applying a patch file would have been even 
>>> easier for you guys.
>> 
>> 
>> Yes - it would. But inserting a new valid xml node is not very 
>> difficult ...
>
>Here it is (as the project is now officially registered at 
>sf.net - zip file will follow shortly).
>
>
>  
>
>This task allows for HelpStudio projects to be 
>created via Ant.
>
>
>  
>Compatibility:
>Ant 1.6.0 and later
>  
>  
>URL:
>href="http://helpstudioant.sourceforge.net";>http://helpstudioant.sourc
>eforge.net
>  
>  
>License:
>GNU General Public License
>  
>
>  
>
>
>-
>To unsubscribe, e-mail: [EMAIL PROTECTED] For 
>additional commands, e-mail: [EMAIL PROTECTED]
>
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

svn commit: r468305 - in /ant/core/trunk: docs/external.html xdocs/external.xml

[jhm]

Author: jhm
Date: Fri Oct 27 00:47:34 2006
New Revision: 468305

URL: http://svn.apache.org/viewvc?view=rev&rev=468305
Log:
Add HelpStudioAnt to external page.

Modified:
ant/core/trunk/docs/external.html
ant/core/trunk/xdocs/external.xml

Modified: ant/core/trunk/docs/external.html
URL: 
http://svn.apache.org/viewvc/ant/core/trunk/docs/external.html?view=diff&rev=468305&r1=468304&r2=468305
==
--- ant/core/trunk/docs/external.html (original)
+++ ant/core/trunk/docs/external.html Fri Oct 27 00:47:34 2006
@@ -756,14 +756,14 @@
 AntPrettyBuild
   
 
-   Ant Pretty Build is a tool to easily show and run Ant 
buildfiles directly from
-   within a browser window. It consists of a single XSL file that 
will generate,
-   on the fly, in the browser, from the .xml buildfile, a pretty 
interface showing
-   project name, description, properties and targets, etc. sorted 
or unsorted,
-   allowing to load/modify/add properties, run the whole project, 
or run selected
-   set of targets in a specific order, with the ability to modify 
logger/logfile,
-   mode and add more libs or command line arguments.
-   
+  Ant Pretty Build is a tool to easily show and run Ant buildfiles 
directly from
+within a browser window. It consists of a single XSL file that will 
generate,
+on the fly, in the browser, from the .xml buildfile, a pretty 
interface showing
+project name, description, properties and targets, etc. sorted or 
unsorted,
+  allowing to load/modify/add properties, run the whole project, or 
run selected
+set of targets in a specific order, with the ability to modify 
logger/logfile,
+mode and add more libs or command line arguments.
+
   
   
   
   
   
+
+HelpStudioAnt
+  
+This task allows for HelpStudio projects to be 
created via Ant.
+  
+  
+  
+  Compatibility:
+  
+  
+  Ant 1.6.0 and later
+  
+  
+  
+  
+  URL:
+  
+  
+  http://helpstudioant.sourceforge.net";>http://helpstudioant.sourceforge.net
+  
+  
+  
+  
+  License:
+  
+  
+  GNU General Public License
+  
+  
+  
+  
 
 IDLDepend
   
@@ -5299,7 +5336,7 @@
 Transformica
   
 Transformica is a versatile and extensible code 
generator.
-   Supports multiple source models including database metadata, Java 
source files, grammar 
+   Supports multiple source models including database metadata, Java 
source files, grammar
files and custom models.
 
   

Modified: ant/core/trunk/xdocs/external.xml
URL: 
http://svn.apache.org/viewvc/ant/core/trunk/xdocs/external.xml?view=diff&rev=468305&r1=468304&r2=468305
==
--- ant/core/trunk/xdocs/external.xml (original)
+++ ant/core/trunk/xdocs/external.xml Fri Oct 27 00:47:34 2006
@@ -356,34 +356,34 @@
   
 
   
-   
-   Ant Pretty Build is a tool to easily show and run Ant 
buildfiles directly from
-   within a browser window. It consists of a single XSL file that 
will generate,
-   on the fly, in the browser, from the .xml buildfile, a pretty 
interface showing
-   project name, description, properties and targets, etc. sorted 
or unsorted,
-   allowing to load/modify/add properties, run the whole project, 
or run selected
-   set of targets in a specific order, with the ability to modify 
logger/logfile,
-   mode and add more libs or command line arguments.
-   
-   
-   
-   Compatibility:
-   All Ant versions
-   
-   
-   URL:
-   http://antprettybuild.sourceforge.net/";>Ant Pretty Build Homepage
-   
-   
-   Contact:
-   http://antprettybuild.sourceforge.net";>Charbel BITAR
-   
-   
-   License:
-   Apache License V2.0
-