Another thing we need to look into is how a user is supposed to generate HiveDoc for custom ModuleDescriptorProviders. It would of course be nice if this were possible with an Ant task. But how should the providers be specified by the user and then later initialized by the task? Requiring a no-arg constructor and no further initialization is not very satisfying...
The best idea I can come up with is to provide a HiveMind service for the HiveDoc generation. The user would have to specify the custom providers as contributions to a defined configuration point. (Of course he can then define the custom providers as services with their own configurations.) In the Ant file it would only be a matter of specifying the path to the module descriptors with the contributions. Now these descriptors have to be in the default XML format! Otherwise the user is more than welcome to write his own HiveDoc generator :-) Anyone got a better idea? --knut --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
