Hi, Didn't mean to post that one to the list but in case anyone else is stuck similarly it turns out that I have an extra space after the true. The plugin does an exact match for true and so deemed it as unset. Trim anyone??
ste ------------------------------------ Stephen Gargan, IT Engineer [EMAIL PROTECTED] Tel: (858) 658-3418 ------------------------------------ -----Original Message----- From: Gargan, Stephen [mailto:[EMAIL PROTECTED] Sent: Monday, January 05, 2004 11:29 AM To: Maven Users List Subject: RE: XDoclet, Struts and Maven: Where to start? SOLUTION Hey Moritz, Sorry for the random drive by mailing, but it seems that I am having the same problem that you had before and I was hoping that you might be able to help me out. I have been trying to get Xdoclet to build my struts-config.xml and though I think I have all the properties set up like you described it still never runs the strutsconfig task. I was hoping you could look at my properties and see if I have anything glaring missing from them. maven.multiproject.type=war maven.xdoclet.webdoclet.force=true maven.xdoclet.webdoclet.mergedir=conf/merge maven.xdoclet.webdoclet.fileset.0=true maven.xdoclet.webdoclet.fileset.0.include=**/*.java maven.xdoclet.webdoclet.deploymentdescriptor.0=true maven.xdoclet.webdoclet.deploymentdescriptor.destDir=${maven.build.dir}/xdoclet/web/META-INF maven.xdoclet.webdoclet.deploymentdescriptor.0.validatexml=true maven.xdoclet.webdoclet.deploymentdescriptor.0.distributable=false maven.xdoclet.webdoclet.deploymentdescriptor.0.mergeDir=conf/merge maven.xdoclet.webdoclet.strutsconfigxml.0=true maven.xdoclet.webdoclet.strutsconfigxml.destDir=${maven.build.dir}/xdoclet/web/META-INF maven.xdoclet.webdoclet.strutsconfigxml.0.validatexml=true maven.xdoclet.webdoclet.strutsconfigxml.0.version=1.1 maven.xdoclet.webdoclet.strutsconfigxml.0.mergeDir=conf/merge maven.xdoclet.webdoclet.strutsvalidationxml.0=true maven.war.webxml=${maven.build.dir}/xdoclet/web/META-INF I've included the following dependencies <dependency> <artifactId>xdoclet</artifactId> <groupId>xdoclet</groupId> <version>1.2b4</version> <type>jar</type> </dependency> <dependency> <artifactId>xdoclet-apache-module</artifactId> <groupId>xdoclet</groupId> <version>1.2b4</version> <type>jar</type> </dependency> <dependency> <artifactId>xdoclet-web-module</artifactId> <groupId>xdoclet</groupId> <version>1.2b4</version> <type>jar</type> </dependency> <dependency> <artifactId>xdoclet-xdoclet-module</artifactId> <groupId>xdoclet</groupId> <version>1.2b4</version> <type>jar</type> </dependency> The struts validation runs but no matter what I try the config task won't run. Could you possibly tell me the properties that u used to get it working, I'd really appreciate it Thanks a lot, Regards, Steve ------------------------------------ Stephen Gargan, IT Engineer [EMAIL PROTECTED] Tel: (858) 658-3418 ------------------------------------ -----Original Message----- From: Moritz Petersen [mailto:[EMAIL PROTECTED] Sent: Sunday, November 16, 2003 9:33 AM To: Maven Users List Subject: Re: XDoclet, Struts and Maven: Where to start? SOLUTION With the help of Marc, I finally found the problem. To let others know what I did wrong, here's the solution for working with webdoclet / strustsconfigxml: - Check the plugin.jelly of xdoclet plugin (you'll see how the properties are processed, search for the subtask, for example "strutsconfigxml"). - Check the plugin.properties of xdoclet plugin (you'll see some properties already defined). - Check the dependencies in your project. Mine are (among others): <dependency> <artifactId>xdoclet</artifactId> <groupId>xdoclet</groupId> <version>1.2b4</version> <type>jar</type> </dependency> <dependency> <artifactId>xdoclet-ejb-module</artifactId> <groupId>xdoclet</groupId> <version>1.2b4</version> <type>jar</type> </dependency> <dependency> <artifactId>xdoclet-apache-module</artifactId> <groupId>xdoclet</groupId> <version>1.2b4</version> <type>jar</type> </dependency> <dependency> <artifactId>xdoclet-web-module</artifactId> <groupId>xdoclet</groupId> <version>1.2b4</version> <type>jar</type> </dependency> <dependency> <artifactId>xdoclet-xdoclet-module</artifactId> <groupId>xdoclet</groupId> <version>1.2b4</version> <type>jar</type> </dependency> -Mo. Am 15.11.2003 um 20:59 Uhr schrieb Moritz Petersen: > Hi Konstantin, > > you gave me very helpful pointers, thank you! But I still can't get it > work. I must have missed something very obvious. > > A look into plugin.jelly discovered: > > ... > > <j:set var="subelement_index" value="0"/> > <j:forEach begin="0" end="20" indexVar="subelement_index"> > <j:set var="subelement_index_var_name" > value="maven.xdoclet.webdoclet.strutsconfigxml.${subelement_index}"/> > <j:if test="${context.getVariable(subelement_index_var_name) == > 'true'}"> > > ... > > So, I added the property > > maven.xdoclet.webdoclet.strutsconfigxml.0=true > maven.xdoclet.webdoclet.strutsconfigxml.0.Version=1.1 > > but it still doesn't work. So I tried additionally: > > maven.xdoclet.webdoclet.fileset.4=true > maven.xdoclet.webdoclet.fileset.4.include=**/*Action.java > > because I thought it would ignore my *Action classes, but it still > didn't made it work. Changing "0" to "4" in the strutsconfigxml > properties also didn't change anything. > I am pretty sure, that my properties are not ignored in general, > because I define properties for other Xdoclet modules > (hibernatedoclet), which are not ignored. > > Do you have any clue about what I am missing? > > Grüße aus Hamburg, > > Moritz. > > > > Am 15.11.2003 um 17:55 Uhr schrieb Konstantin Priblouda: > >> I think you shall bite into sour apple, and look into > > I like apples, especially those running Panther ;-) > >> plugin.jelly >> for exact syntax... >> Basically properties are in form >> maven.xdoclet.<module>.<subtask>.<ordinal >> number>.<subtask property> >> >> And ordinal number starts from 0. >> Also importtant is: >> maven.xdoclet.<module>.<subtask>.<ordinal >> number>.enabled=true >> >> to activate subtask. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]