Hi
Nicolas Chalumeau wrote:
I was looking at the existing xdoclet2 maven 1 plugin. It seem to be
dependant of ant XDocletTask extends AbstractGeneramaTask that extends
PicoContainerTask)
So I want to know what are the best practise when writing a mojo (it
is more a m2 team question I add xdoclet to inform them) :
- totaly rewrite it to be independant of any ant task
- create wrapper of the existing ant task
- don't use a mojo but an other langage marmalade...
The first solution seem a bit idealist and the second link a mojo to ant.
If I could have some feed back of what other do (I remember that
Vincent work on it for cargo)
I believe Vincent is going for option 1. It is the idealistic approach,
but if it works for you, you should be able to reuse all the actual
logic and make the ant tasks and maven plugin "views" over the same
code. So it is definitely recommended.
2 and 3 are about equivalent, and its really up to you which you prefer.
I would say going to marmalade would be if you wanted to use a lot of
pre-existing ant tasks, not just your own.
Hope this helps.
- Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
