Response inline >The way that I went about something similar was to create a custom xdoclet module. >It's fairly >trivial to create a task that simply uses your xdt files. You can then package this >module and >deploy it to your ANT_HOME/lib (like your other xdoclet modules). Then you simply >direct your >plugin to use this new ant task.
ok.. could you please forward to me an example of a simple xdoclet module, i tried it but it looked rather complicated to me even if i didn't put that much time into it since i was using ant and i realized that using a xdt was faster >> 2 ) In my plugin i have to call xdoclet:ejbdoclet as prerequisite, so i need to >> have a >> project.properties that contains the appropiate xdoclet config parameters. The >> problem is that >> this configuration are read only from the project.properties file in the final >> project directory >> and not from the one in the maven plugin directory that uses xdoclet plugin. >> >If I understand you correctly, you mean that the project (or build) .properties files >in the >project that uses the plugin are overriding the plugins default properties (which >should be >defined in plugin.properties). This is the way in which Maven is designed. If you do >not want the >plugin's properties to be overriden, then you need to not include them in the >project's >properties. This is not exactly what's happening.... I am saying that I do not have any xdoclet properties defined in the project that uses my plugin, i do have a project.properties defined in my plugin with all the xdoclet property defined in it.. but when i call xdoclet:ejbdoclet those are not used... and the default are Thanks Max --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
