ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniels, Doug" <Doug.Dani...@gdc4s.com>
Subject RE: Google Summer of Code, Apache ANT project ideas?
Date Fri, 03 Jun 2005 19:24:33 GMT
Yeah I was way off on Velocity I thought it was part of XDocs but really its that servlet engine.
What's wrong with XDocs it seems like a good way to parse through the Ant Tasks meta-data
javadoc comments and extract the information we need for documentation. What other types of
capability were you looking for?

The project deliverable would most likely be an Ant Task that could perform this document
auto-generation right?

Where can I find the previous XDoc stuff that was developed?

Doug Daniels


-----Original Message-----
From: Erik Hatcher [mailto:erik@ehatchersolutions.com]
Sent: Friday, June 03, 2005 2:09 PM
To: Ant Developers List
Subject: Re: Google Summer of Code, Apache ANT project ideas?


Doug - I've added it as project ID ant-xdocs to that wiki page.  As  
for technologies - I'm not sure if Velocity and XDoclet are the best  
technologies to use right now.  Let's solicit input from others here  
on their architecture ideas.

     Erik

On Jun 3, 2005, at 1:46 PM, Daniels, Doug wrote:

> Erik,
>
> Sounds great, maybe you can submit it on the Apache SoC proposal  
> page(http://wiki.apache.org/general/SummerOfCode2005), and I'll  
> submit my application to google with Apache as my selected  
> organization.
>
> I guess I'd propose it something like:
> The Apache Ant project needs a way to auto-generate task/type  
> documentation. The proposed solution would use Velocity and xdocs  
> to create a standard way to document the old and new Ant tasks to  
> keep the documentation up to date and easily updatable in the  
> future automatically.
>
> By the way I have your book and it was a great help with what I've  
> been working on at my job. I was thinking of writing up an Ant  
> tutorial describing an interesting build system we came up with  
> utilizing Ant's import task to create a common build hierarchy  
> infrastructure, that can be extended to new products very easily.  
> It really helps when we have to add a new product in and all we do  
> is define some properties and throw a build.xml stub in and it is  
> then included into our software package.
>
> Doug Daniels
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> For additional commands, e-mail: dev-help@ant.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


Mime
View raw message