ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Erik Hatcher" <>
Subject XDoclet status update
Date Sun, 03 Mar 2002 02:27:56 GMT
I've enhanced the proposal/xdocs a bit to detect Ant tasks a lot better. It
climbs the hierarchy looking for a parent class with an execute() method
(except if it hits it quits and doesn't count that
as a task).

I'm using the generation of as the "litmus test" to how
good the generation is working, and it just about matches our currently hand
maintained  Here are the exceptions:

XDoclet generates these extras: (any reason
not to make this abstract?) (this
couldn't really be used by a task because of the exceptions its execute
method throws, right?  Or does that matter?) (it also generates the
correct mapping to EmailTask, perhaps need an 'ignore' flag?) (these
are really tasks, but we have no mappings to them - why not?)
(both are the same, essentially. Can we deprecate VAJLoadProjects?)
(Currently these look and smell like tasks, but their execute method throws
Exception - does that take them out of the running to really be tasks?)

XDoclet omits these: (all
of these are @deprecated) (several mappings to the same
class - need to handle this situation with XDoclet - shouldn't be a problem) (need
to resolve issue from above)

I can easily bring the deprecated classes back to life, I just thought for
grins that I'd let it ignore them for now. I don't want to start a big
"deprecation" discussion again, and certainly removing deprecated classes
from the mappings file breaks backwards compatibility, so we'll have to
re-enable for the real thing.

Overall, it looks like its right on track with only a few minor issues.
Here are a few issues/ideas:

- Can a class with a method 'void execute() throws Exception' be a task?

- It seems that we have a few exceptions that will require an 'ant.task
ignore="true"' kinda thing so that it gets skipped over for processing even
though it could really be used as a task.  Thoughts?

- There are several tasks that point to Expand, and right now there are
additional 'name="..."' in the class, but the template is not coded such
that it picks that up when building  This should be an
easy thing to add.  But how would multiple names play out in the XML created
for a task?  Should it create multiple XML files?  Or just note the multiple
names as aliases in one XML file somehow?

- Categorization - should we restrict a task to a single category?  Or allow
it to be in multiple?  Or do we need a few different "bucket" types to drop
tasks into?  I've been thinking we should have a "vendor" bucket so that we
could create groupings in documentation for all Weblogic tasks (wljspc,
wlrun, wlstop) for example.  There are lots of ways we could go with this!
So start the brainstorming, and let me know.


To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

View raw message