On Tue, 25 Mar 2003, Steve Loughran [EMAIL PROTECTED] wrote:
I am sure we could probably do a PDF build from the xdocs stuff now,
I'm sure, too.
if we somehow create docbook content via XSLT, velocity, whatever.
Why docbook? You could create the XSL:FO directly, no?
Please note that this
On Tue, 25 Mar 2003, Stefan Moebius [EMAIL PROTECTED] wrote:
warning: unportable BRE: `^/.*': using `^' as the first character of
the basic regular expression is not portable;
That's funny.
The GNU man pages of expr(1) are a bit vague here (they talk about
anchored expressions in context of
Hi All
I'm currently cleaning up a huge repository of source
files which have all kinds of line endings. So I had a
look at the FixCrLf task. Although FixCrLf basically
does what I'm looking for I need some more features:
a) checkout all the files with a wrong line ending
b) fix them
c) check
On Wed, 26 Mar 2003, Neeme Praks [EMAIL PROTECTED] wrote:
Stefan Bodewig ::
On Sat, 01 Mar 2003, Neeme Praks [EMAIL PROTECTED] wrote:
storeElement() method silently returns, if the tag does not support
the specified element.
This is because storeElement can never be called without calling
Hi All,
(Please forgive my newbie-ness).
I have developed an Ant Task for the Artima SuiteRunner and I'd like to
submit it. Perhaps a Committer might a respond directly and I'll e-mail them
a zip file containing the code? (Didn't want to send a zip file to a few
hundred people...!)
Thanks,
This email is autogenerated from the output from:
http://cvs.apache.org/builds/gump/2003-03-26/test-ant.html
Build results exceed maximum length.
Please see URL above for details.
Last 50
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18363.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Hi,
Myself and Leigh Ishikawa (Adding 'setName' support to the
xmljunitresultformatter.java) have not received any response to our
contributions. Can someone please advise?
Cheers,
Adam
-Original Message-
From: Adam Duffy [mailto:[EMAIL PROTECTED]
Sent: 26 March 2003 11:09
To: Ant
Could someone please explain me what SuiteRunner brings to the table that
JUnit doesn't I've looked at it quite a bit, and maybe beside better
reporting, I don't see anything compelling about it compared to JUnit, and
even loose the built-in assert methods of TestCase (thru Assert)...
I'd be
Hi Dominique,
I would like to know what other people think too.
If at the end of the day, the developers of Ant do not wish to use the code
I have written, that is fine with me. I only want to contribute to the
development of Ant - which I am really fond of. As does Leigh Ishikawa. Any
advice on
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18363.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8080.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
bodewig 2003/03/26 07:50:28
Modified:src/main/org/apache/tools/ant/taskdefs/optional/unix
Symlink.java
Log:
Fix javadocs.
PR: 17143
Submitted by: Gus Heck
Revision ChangesPath
1.4 +7 -7
Thanks Dominique,
I wasn't aware of that policy regarding 'external' tasks (since I only
started subscribing recently). I'll ask Artima.com to see if their
interested. :)
Thanks again,
Adam
-Original Message-
From: Dominique Devienne [mailto:[EMAIL PROTECTED]
Sent: 26 March 2003 15:37
On Wed, 26 Mar 2003, Adam Duffy [EMAIL PROTECTED] wrote:
Myself and Leigh Ishikawa (Adding 'setName' support to the
xmljunitresultformatter.java) have not received any response to our
contributions. Can someone please advise?
First advice would be to be more patient, four hours isn't that
That said (by Erik and myself), if SuiteRunner becomes popular enough (like
JUnit), and even though it's an 'external' task, there would be a good
possibility that it could be incorporated in ant-optional.jar, simply to
help and evangelize Unit Testing in general, which is a best practice.
That
Hmm I notice that the source is marked as experimental and subject to
change. Is this still true? To what extent. I am slightly leary of
upgrading to an alpha branch for our builds, particularly if the
compelling feature is going to be a moving target :)
Also in your example buildfile, I am
subant is stand alone (not the very latest version with the dependency
stuff), i.e. a single Java file. The version integrated to Ant removes the
magic of inferring the target to call from the current target (which is why
you thought all the targets do the same thing... They all call a different
On Wed, 26 Mar 2003, Dominique Devienne [EMAIL PROTECTED] wrote:
That said (one more ;-), if Ant ever comes up with an easier way to
integrate third party tasks
Easier than taskdef resource=...classpath ...//taskdef?
Almost impossible.
Stefan
Hu, not totally. If the AntLib also uses types, you need another
typedef, which should also probably needs a loaderref. Since you now use
twice the classpath, if needs to be outside and refid'd.
And what about the junit task? I'd like to not have setup my classpath
outside of Ant and
I meant ANT_HOME/lib. --DD
-Original Message-
From: Dominique Devienne [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 26, 2003 10:37 AM
To: 'Ant Developers List'
Subject: RE: Artima SuiteRunner Task
Hu, not totally. If the AntLib also uses types, you need another
typedef, which
On Wed, 26 Mar 2003, Dominique Devienne [EMAIL PROTECTED] wrote:
Hu, not totally.
Did I forget to put that smiley in?
Since you now use twice the classpath, if needs to be outside and
refid'd.
No, you'll need to use the loaderref attribute.
And what about the junit task?
Easy in Ant
Regarding suiterunner vs JUnit, I prefer the suiterunner API:
test methods can throw Exceptions, also assertion failures generate
Exceptions so you can put one catch(Exception) at the bottom of your method and
print out any useful info before throwing the exception on, rather than
-Original Message-
From: Erik Hatcher [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 26, 2003 11:55 AM
To: Ant Developers List
Subject: Re: Artima SuiteRunner Task
snip
test and batchtest in Ant support if/unless properties
and I always
have it set up to be able to run a
I do it with one line in my build.xml:
test todir=${junit.results} name=${testcase} if=testcase/
and a small change to the batchtest task:
batchtest todir=${junit.results} unless=testcase
Both of these in are my test target, so I just run ant with
ant -Dtestcase=com.whatever.TestWhatever test
Ah - ok.
And proof that no matter how tattered the pages of my copy of JDWA are,
there's more gems to be found within.
Thanks!
Chris
-Original Message-
From: Steven Newton [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 26, 2003 12:05 PM
To: Ant Developers List
Subject: RE:
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16455.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
I don't buy that. If your exception doesn't contain enough info, then modify
the exception. I never trap exception in Unit tests, unless I'm expecting it
to be thrown and fail() if it doesn't.
As far as running one of more tests, I use a
-Dtestcase=com/acme/SomeTest.class, and testcases
Dominique Devienne wrote:
Hu, not totally. If the AntLib also uses types, you need another
typedef, which should also probably needs a loaderref. Since you now use
twice the classpath, if needs to be outside and refid'd.
In ant1.6 the difference between tasks and types is very small. It
stevel 2003/03/26 09:55:37
Added: docs/manual/CoreTasks subant.html whichresource.html
Log:
manual insertion of xdocs pages
Revision ChangesPath
1.1 ant/docs/manual/CoreTasks/subant.html
Index: subant.html
Stefan Bodewig wrote:
On Tue, 25 Mar 2003, Steve Loughran [EMAIL PROTECTED] wrote:
I am sure we could probably do a PDF build from the xdocs stuff now,
I'm sure, too.
if we somehow create docbook content via XSLT, velocity, whatever.
Why docbook? You could create the XSL:FO directly, no?
I
Chris Reeves wrote:
Ah - ok.
And proof that no matter how tattered the pages of my copy of JDWA are,
there's more gems to be found within.
Thanks!
Chris
I believe that particular snippet is a near-direct cut and paste from
ant's own build file. So the credit goes to whoever set up the junit
Costin Manolache wrote, On 26/03/2003 18.46:
Dominique Devienne wrote:
Hu, not totally. If the AntLib also uses types, you need another
typedef, which should also probably needs a loaderref. Since you now use
twice the classpath, if needs to be outside and refid'd.
In ant1.6 the difference
I would include filters, mappers, conditions and selectors to
the list.
A relatively simple mod to the core ant makes this
possible (bugzilla 17199) basically get ConditionBase.java,
AbstractFileSet, FilterChain implement DynamicConfigurator.
and get UnknownElement (bugzilla 18312) call
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18166.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18312.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18312.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18312.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18312.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
peter reilly wrote:
I would include filters, mappers, conditions and selectors to
the list.
I would exclude them :-)
Taks, types, mappers, filters, whatever are just ant components -
and they shouldn't need a special syntax from user perspective.
We shouldn't treat them ( or types, tasks )
After much head scratching, I came up with a solution to my own little Ant
extension problem (about which I complained about a few months back).
Basically, I first had to use Parametrizable to enable the extension point,
like other Ant types:
buildpath ident=buildpath
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18391.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18391.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
ok, fair enough. I sent a patch to commons-dev with a workaround for
Jelly anyway... just have to check back now if the patch was actually
noticed or not ;-)
Stefan Bodewig ::
On 26 Mar 2003, Stefan Bodewig [EMAIL PROTECTED] wrote:
I'm going to throw in the extra check in CVS HEAD later
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18391.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18391.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18391.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
47 matches
Mail list logo
