Hi all,
the CDK build system is Ant oriented (not religiously, just historically) and
consists of two important steps:
- determine which CDK class belongs to which module
- compile all modules
The first step has long be done using a custom JavaDoc Doclet. However, there
were a few problems with this approach:
- compiling the doclet was different for Java versions and platforms
- was talking a lot of memory (Rajarshi recently addressed that)
- the output was confusing people (gave warnings about missing jars)
So, I set down last night to write a custom application that parses all Java
Source files and extracts the @cdk.module, @cdk.set and @cdk.require
information to create the *.javafiles and *.set files in ${build}. See
revision 6867.
The JavaDoc version was nice as it properly parsed the Java source; my script
just does some grepping, and is more error prone. BTW, the change should show
a considerable speed up of the runDoclet target.
So, if you are using the CDK from SVN, please give the new system a good go,
and let me know if you find problems.
Egon
--
CUBIC
blog: http://chem-bla-ics.blogspot.com/
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Cdk-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/cdk-user
