You don't need to have anything special specified in maven.xml if you invoke a goal directly (as in maven xdoclet:ejbdoclet as you are doing). However where via an ant projectfile you would specify the target and supply all the relevant xdoclet subelements and properties, when using the xdoclet plugin from maven, it is the xxxx.properties which drives everything, that is, controls the plugin behaviour.
It is probably done best on a project by project basis so therefore the properties file to modifiy is your project.properties (as opposed to $HOME/build.properties or <project>/build.properties) The default plugin properties are as at http://xdoclet.sourceforge.net/maven-plugin.html and point "3. Now how does XDoclet know you want to run remoteinterface subtask..." [A snippet from my project.properties] # set up xdoclet to process this subset of files maven.xdoclet.webdoclet.fileset.0=true maven.xdoclet.webdoclet.fileset.0.include=**/*Form.java maven.xdoclet.webdoclet.fileset.1=true maven.xdoclet.webdoclet.fileset.1.include=**/*Action.java # Generate a webapp descriptor pulling in merge data from metadata/web maven.xdoclet.webdoclet.deploymentdescriptor.0=true maven.xdoclet.webdoclet.deploymentdescriptor.0.validateXML=true maven.xdoclet.webdoclet.deploymentdescriptor.0.distributable=false maven.xdoclet.webdoclet.deploymentdescriptor.0.displayname=${pom.name} maven.xdoclet.webdoclet.deploymentdescriptor.0.mergeDir=metadata/web # Generate a struts config descriptor pulling in extra data from metadata/struts maven.xdoclet.webdoclet.strutsconfigxml.1=true maven.xdoclet.webdoclet.strutsconfigxml.1.validateXML=true maven.xdoclet.webdoclet.strutsconfigxml.1.Version=1.1 maven.xdoclet.webdoclet.strutsconfigxml.1.destDir=${maven.build.dir}/web/WEB-INF maven.xdoclet.webdoclet.strutsconfigxml.1.subTaskName=Generating struts-config.xml maven.xdoclet.webdoclet.strutsconfigxml.1.mergeDir=metadata/struts # Generate a struts validation descriptor maven.xdoclet.webdoclet.strutsvalidationxml.1=true maven.xdoclet.webdoclet.strutsvalidationxml.1.destDir=${maven.build.dir}/web/WEB-INF maven.xdoclet.webdoclet.strutsvalidationxml.1.subTaskName=Generating struts-validation.xml The above definitions map directly to how you would specify the webdoclet target and required subelement attributes in an ant project file. These following definitions set plugin behaviour for using xdoclet to generate jsp templates and application resource snippets from the form beans. Multiple nested elements are defined using indices 0 .. 9 (pretty nifty little trick snaffled from Erik Hatcher) maven.war.webapp.dir=${maven.build.dir}/web/ maven.xdoclet.xdoclet.force=true maven.xdoclet.xdoclet.destDir=${maven.src.dir}/gen maven.xdoclet.xdoclet.fileset.0=true maven.xdoclet.xdoclet.fileset.0=${maven.src.dir}/web/**/${form.name}.jsp maven.xdoclet.xdoclet.template.0=true maven.xdoclet.xdoclet.template.0.templateFile=templates/simple/FormKeys.xdt maven.xdoclet.xdoclet.template.0.ofType=org.apache.struts.action.ActionForm maven.xdoclet.xdoclet.template.0.acceptAbstractClasses=false maven.xdoclet.xdoclet.template.0.prefixWithPackageStructure=false maven.xdoclet.xdoclet.template.0.destinationFile={0}.properties maven.xdoclet.xdoclet.template.1=true maven.xdoclet.xdoclet.template.1.templateFile=templates/simple/StrutsForm_jsp.xdt maven.xdoclet.xdoclet.template.1.ofType=org.apache.struts.action.ActionForm maven.xdoclet.xdoclet.template.1.acceptAbstractClasses=false maven.xdoclet.xdoclet.template.1.prefixWithPackageStructure=false maven.xdoclet.xdoclet.template.1.destinationFile={0}.jsp Hope this helps Robbe Stewart > -----Original Message----- > From: Marco Tedone [mailto:[EMAIL PROTECTED] > Sent: Tuesday, 16 March 2004 5:35 AM > To: XDoclet-users > Subject: [Xdoclet-user] How to use Maven plugin > > > Hi, I'm reading the documentation on the XDoclet website > about the Maven > plugin. However, I don't know what the "xdoclet:ejbdoclet" > goal expects in > the maven.xml file. I've got a folder /src under which java, > webapp, etc. > are stored. When I point my cursor to /src and type "maven > xdoclet:ejbdoclet" nothing happens. > > I had an Ant file with an ejbdoclet element defined in it. I > specified all > the patterns in there, and it was working fine. I guess the > xdoclet Maven > plugin avoids us from specifying an ejbdoclet target in our > maven.xml, and > the use of the properties should drive how the application applies the > transformation patterns. > > Could anyone please initiate me on this? > > Thanks, > > Marco > > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > _______________________________________________ > xdoclet-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/xdoclet-user > ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
