First, maybe check this page out :
http://docs.codehaus.org/display/XDOCLET/Maven2+plugin
Thanks for the pointer , great info that until now I didn't know existed.
That's true but
1) they won't have to declare any of the depencies on and of xdoclet
itself, which was the case with maven1 or ant.
Absolutely, I agree, this is a great improvement in m2.
2) these dependencies on your xdoclet-plugins will be declared in the
pom/plugins/plugin/dependencies section, so they won't be an actual
dependency of your user's poms.
You taught me something new. Even though I have written a couple Mojos already, I didn't read the POM spec carefully enough to realize that's where you declared plugin-specific dependencies. Thanks.
You *could* do that, but that seems far fetched to me. You probably
wouldn't need to extend the mojo class itself anyways, but rather just
declare dependencies to your xd-plugins, but creating a maven-plugin
for that, or just a parent pom probably comes down to the same thing.
I think I'll try the parent POM method first, with the dependency declared in the plugin section of the POM.
Don't hesitate to comment more, express feature requests, or, of
course, provide patches ;)
I'll try the plugin tonight or tomorrow, and rest assured, I'll let you know if something doesn't work :-). Thanks for the plugin and the help.
Shash
