+1
for 3, I'd reuse whatever Ant uses, or stick with something simple and
handcrafted. I'm not sure you need to invest too much time writing
something new.
Cheers,
Brett
On 14/06/2008, at 8:50 AM, Dennis Lundberg wrote:
Hi
I'm in the process of converting the Ant builds, at my day job, to
use Maven Ant tasks for dependency management. This is my first
contact with Maven Ant tasks so I gave the doc a thorough reading
and made some corrections and alterations. The doc is currently only
one page [1] and is part of the maven site.
The page is very long and tries to cover everything there is to know
about the Ant tasks. Unfortunately it doesn't cover everything, as
I've seen going through the user list trying to find answers. So I'd
like to make some changes to the documentation.
1. Move the docs from maven site to the Ant tasks, in subversion.
2. Split up the current one page into several more focused pages.
3. Create a reference section, similar in function to the
documentation for Ant, to make it easier for Ant (=non-Maven) users
to find their way.
Thoughts, ideas, criticism?
For 3 I thought I'd have a look at how Ant currently generates its
own documentation. One possibility would be to use annotations and
create a Maven plugin to extract those along with Javadoc to create
general documentation for Ant tasks (not just the Maven Ant tasks).
This would work similarly to how the plugin-plugin works on Maven
plugins.
Is this a feasible approach or just a waste of time?
[1] http://maven.apache.org/ant-tasks.html
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
