Pfffew, that was close, the JJTree doc was half written when I saw your post.
For Conor, here is the doc for MParse.
It is deprecated anyway, it was coded to run with MParse 1.1. I didn't test it because I don't have 1.1 available in my computer and it would certainly ruin my 2.0 install.
Change are required to make it work with 2.0. lib changed and parameters are differents.
This should not be a big problem to make a task for 2.0 but I think that there is about 10% of the current code that will be used for 2.0.... That will be a complete rewrite.
Should we do that during beta 2 stage ?
--
St�phane Bailliez
Software Engineer, Paris - France
iMediation - http://www.imediation.com
Disclaimer: All the opinions expressed above are mine and not those from my company.
> -----Original Message-----
> From: Michael Saunders [mailto:[EMAIL PROTECTED]]
> Sent: Monday, February 12, 2001 4:52 PM
> To: [EMAIL PROTECTED]
> Subject: Re: 2nd Beta
>
>
> Conor,
>
> Attached is the doc for jjtree. It doesn't give much more
> than the available
> options but I guess it is better that nothing.
>
> Michael
>
> Conor MacNeill wrote:
> >
> > I will be producing a second beta in a few days. I am
> currently waiting on
> > the following
> >
> > 1. Updated documentation for wlrun and wlstop (me)
> > 2. Updated <project> element in VAJ tasks (Glenn)
> > 3. Update to tar in 1.3 branch and decision about
> omit/truncate (Sam)
> > 4. javah documentation (I have mailed the author)
> > 5. mparse documentation (Stephane?)
> >
> > Would someone like to document the <starteam> task please? How about
> > <jjtree> ?
> >
> > Once the beta is tagged, I will merge the latest changes
> into the MAIN
> > trunk.
> >
> > This second beta will be the release candidate unless there
> are some major
> > bugs reported. I'll probably extend the release plan by a
> few days to give
> > everyone enough time to hit it.
> >
> > Conor
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
>
Title: JavaCC Task
MParse
Requirements
This task requires Metamata Development environment 1.1. It does not work as is with the latest 2.0 version freely available at Metamata.
Description
Invokes the Metamata MParse compiler compiler on a grammar file.
To use the mparse task, set the target attribute to the name of the grammar file to process. You also need to specify the directory containing the Metamata installation using the metamatahome attribute, so that Ant can find the MParse classes.
This task only invokes MParse if the grammar file is newer than the generated Java files. MParse assumes that the Java class name of the generated parser is the same as the name of the grammar file, less the .jj extension.
For additional information about MParse, please consult the online manual available here (PDF)
Parameters
| Attribute | Description | Required |
| target | The .jj grammar file to process. It will only be processed if the grammar is newer than the corresponding .java file. | Yes |
| metamatahome | The home directory containing the Metamata distribution. | Yes |
| workingdir | The temporary directory used by MParse. | Yes |
| cleanuphack | Remove the stale file as well as the intermediate Sun JavaCC file created during the transformation of the grammar file. | No. Default to false. |
Nested elements
userclasspath
The userclasspath element is required and represents a PATH like structure.
Example
<mparse target="src/Parser.jj" metamatahome="c:/metamata" workingdir="c:/tmp">
<userclasspath>
<pathelement location="./lib/dependency.jar"/>
</userclasspath>
</mparse>
This invokes Metamata MParse installed in c:/metamata on a grammar file src/Parser.jj with a working directory in c:/tmp and a specific classpath
