On 3/2/06, Kohsuke Kawaguchi <Kohsuke.Kawaguchi_at_sun.com> wrote:
>
> Malachi de Ælfweald wrote:
> > but from the XJC command line (which is where I took the specs from) it
> says
> > that each one has to be listed on the command-line; whereas you don't
> have
> > to list each XSD... The underlying Driver handles them differently...?
>
> Ah, good point, yes. There's a bit of asymmetry. If the recursive search
> semantics is nice-to-have for binding files, then we can do that as well.
I don't personally use external binding files, but I have found it to be
extremely useful to just specify the src/main directory for the XSDs instead
of listing them specifically or specifying any regex. I think doing that for
the binding files could make things easier for the Mojo development as well
as the CLI syntax. Assuming of course they want to list all of the binding
files :)
>> I really want just one Maven2 plugin with one syntax. I'm just trying to
> >> better understand what syntax works better.
> >
> > I understand. But, realistically, if we do make a Maven2-specific
> plugin;
> > won't the Ant task still have to be maintained for Ant-users?
>
> Yes, no, all I'm saying is that I just want one CLI, one Ant, and one
> Maven plugin (well two actually --- one Maven1 plugin and one Maven2
> plugin.), and not two Maven2 plugins.
>
> And I think we'd like to minimize the effort of maintaining those
> separate entry points.
I can't agree more. If we can set it up so that we only have to maintain it
in one place, that would be ideal. Short of that, 1 per tool/version would
be best. I was not recommending having two Maven2 plugins -- I think what
you are referring to what me suggesting that an optional maven2 tag could be
to specify an external ant build.xml file that contained the XJC
configuration for those that wanted ant syntax... but I agree with both of
you that could make it confusing.
Malachi