On Fri, 2006-01-20 at 13:16 -0600, Jesse McConnell wrote:
> javacc and sablecc are themselves not particularly large
> plugins...they are mostly just param gathering for executing the main
> class..
> the only other real shared part aside from the basic mechanism of
> gathering and assigning those params is the DirectorySourceScanner
> code...which might be pulled up into that plugin helper object we kick
> around from time to time..
The common use of the plexus api in each of these is to compare
timestamps with the generated code and not run the underlying generator
if it's not needed. Each of them include a parameter to set this
timestamp temp directory, a stale millisecond variable which defaults to
0, and a source and output directory which default to src/main/<plugin-
name> and ${project.build.directory}/generated-sources/<plugin-name>,
respectively.
> it might be interesting to have a general source generation plugin for
> these plugins that combine them all up into different goals
> though...would reduce the number of them floating around :)
>
> jesse
>
> On 1/20/06, Brett Porter <[EMAIL PROTECTED]> wrote:
> Is there value in setting these up to all work off the same
> base?
>
> - Brett
>
> Anthony Vito wrote:
> > Good day everyone,
> >
> > I was wondering if there is any interest in a JLex plugin.
> I have
> > completed one that allows for the same functionality as the
> jlex ant
> > task, with the additional concepts ( and borrowing much
> code ) from the
> > javacc and sablecc plugins. If there is interest, I will
> gladly submit
> > it to Jira. Thanks.
> >
> >
--
Anthony Vito <[EMAIL PROTECTED]>
