cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Donald Ball <ba...@webslingerZ.com>
Subject Re: Different problem compiling 1.6-dev
Date Fri, 10 Dec 1999 20:41:27 GMT
On Fri, 10 Dec 1999, Stefano Mazzocchi wrote:

> Well, I love Ant and I'm dedicated to make the Cocoon build script rock
> solid so that you people don't complain anymore <grin> :)

Well heck, I was trying to make your life easier. I'll stop that now. :)

> Here are my patches to Ant:
> 
> [add] <replace> changes tokens in files: allows us to set @@version@@
> instead of "1.6-dev" and keep everything in one place.
> 
> You command line people will love me, you IDE people a little less, but
> we can live with "Cocoon @@version@@" during development. (I'm an IDE
> person in case you wanted to know, but I want something that builds
> everywere.
> 
> [update] <javadoc2> finally makes javadoc smart!!!! You can now tell
> package="org.apache.cocoon.*" and it will javadoc all your matching
> packages. Gee, it took me 5 years to patch this! First bug I ever found
> in jdk 1.0a was "javadoc com.stefano.*" Boom: please send bug report.
> You guys will love me when you'll use this on other projects.
> 
> [add] <java> calls a java application using reflection and recycling the
> same JVM (which is _incredibly_ faster than make or any other scripting
> tool!!!). Also it allows us to compile Ant without requiring to have all
> the jar stuff in the Ant classpath. (I'm considering to use this trick
> for Cocoon components as soon as I evalutate it's performance).

Does this message mean that you've patched ant (if you have, can you check
the patches into jakarta's CVS) or patched build.xml for cocoon (same
caveat)?

- donald


Mime
View raw message