- 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]