the example I posted comes from an ant build.xml file, not a maven.xml file, there's no jelly involved. Also, jelly never sees the source file, in this kind of thing jelly never sees the content of source files, it only directs them to javadoc.

I've been reading about xjavadoc now being able to read @web.servlet.mapping as @web.servlet-mapping, which helps to get rid of the javadoc bitching about the xdoclet tags. I've tested it, it seems to work ... at least for xdoclet-1.2

J�rg Schaible wrote:

Kevin Hagel wrote on Wednesday, March 10, 2004 8:25 AM:



here's a section of my build file that javadocs:

           <!--
            Try to get JavaDoc to shut the hell up about the
XDoclet tags.
            -->
           <tag name="web.servlet" scope="overview" enabled="false"/>
           <tag name="web.listener" enabled="false"/>
           <tag name="web.filter" enabled="false"/>
           <tag name="hibernate.property" enabled="false"/>
           <tag name="hibernate.class" enabled="false"/>
           <tag name="hibernate.id" enabled="false"/>
           <tag name="todo" scope="all" description="To do:" />

the problem is: while @web.servlet will be successfully ignored,
@web.servlet-mapping will not, something about the hypen in
"servlet-mapping". Javadoc advises using something like
@web.servlet.mapping, but that's not really very useful for
us is it? I suspect javadoc was written by C++ programmers ;-)



Well, before pointing at javadoc, you might consider Jelly <g> IMHO it tries to evaluate the expression "servlet-mapping" ;-)

Regards,
J�rg

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



Reply via email to