From what I can tell the only reason the config target depends on java is so that the build.java directory gets created. It's lazy to couple these two tasks together when you could factor out the "config" vs the "generate" tasks. I believe these tasks could have been better thought out but this is not an Ant book per se. But I fail to see why for instance it is necessary to build your java code before you generate artifacts from the source code.

The material in the book is of a very high standard it would be nice to see Ant used in such a way as well ;-)

Here's another question I had which I sent to the webwork list in case the author is listening.

On page 171 the clean target doesn't remove the generated artifacts.

Does Xdoclet always regenerate them?

It's probably better to always remove things that were there previously at the beginning of the task that's about to put them there now.

What is it that the copy task after the java task actually suppose to be copying?

Here's why it's confusing for me.

On the first javac destdir is specified so that's where the .classes go.

On page 171 there's a copy task after the hibernatedoclet task
and it too specifies destDir implying that the files xdoclet creates
end up in the destDir so why then is there a copy task after it
that copies those files to build.java?

Is there some bug that causes both javac and hibernatedoclet to not obey destdir?




------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user

Reply via email to