Hi,

thanks for the pointers.
I have managed to make it work in a non-generic way (first things first).

This requires two minor changes:
1. In PackageManger.java, method private void parse(String directory)
String[] includes = { "**/*.java" };
is now
String[] includes = { "**/*.java", "**/*.jj", "**/*.jjt" };

2. In JXR.java, method public static boolean isJavaFile(String filename)
return filename.endsWith(".java") && file.length() > 0;
is now
return ( filename.endsWith(".java") || filename.endsWith(".jjt") ||
filename.endsWith(".jj") ) && file.length() > 0;

I guess that a generic solution means to define a property for the
plugin and use it in the two classes above. That's fine with me,
except that jj and jjt are the only types that can really be used with
JXR. What's the point of a code transform is the file is not Java
related.

A trade-off could be some boolean properties like includeJJFile and
includeJJTFiles to decide wether or not to display the files.

Let me know what you think.

regards,

Arnaud

PS: on a different topic, I am trying to use the Javacc plug-in to
transform my .jj into Java files. But the plug-in seems to assume 1 jj
per project or all the jj in the same folder. My project has a lot of
small parsers (some nested inside others). Currently, I am using ant
for that. I am curious to see if there is a clean way to do that with
Maven.



On Sun, 21 Nov 2004 17:31:49 -0800, Michal Maczka <[EMAIL PROTECTED]> wrote:
> Arnaud Sahuguet wrote:
> 
> 
> 
> >Hi,
> >
> >I have a couple of jj and jjt files in my project.
> >When generating the site documentation, these files do not appear
> >because they are not java files (that's my guess).
> >Is there a way to have them appear in the xref documentation?
> >
> >
> >
> >
> XREF is in my opinion quite useless on its own without other plugins
> using it (like checksyle, pmd).
> If you want simply to provide a link to web page showing your source
> code/grammar you can simply link to
> pages produced by viewcvs or such tool.
> 
> One thing which imo might be useful in case fo javacc is a grammar
> explication/documentation generated by JJDoc  - it should not be that
> hard to add support for it.
> 
> Michal
> 
> ----------------------------------------------------------------------
> Ponad 400 tysiecy facetow czeka na Ciebie
> >>> http://link.interia.pl/f183a
> 
> 
> 
> 
> ---------------------------------------------------------------------
> 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