Sure...
I would rather do:
<configuration>
<extension>org.eoti.codemodel.ImplementToJAXBElement</extension>
<extension>org.eoti.codemodel.ExtendMyBaseClass</extension>
<strict>false</strict>
</configuration>
and assume a default src/target directory based on maven standards
(src/main, target/jaxb), not use any filesets, not use regex, classpaths,
etc....
Mal
On 3/2/06, Kohsuke Kawaguchi <Kohsuke.Kawaguchi_at_sun.com> wrote:
>
> I figured out how to do this. I can now have the user write:
>
> <configuration>
> <!-- mostly the same syntax as Ant -->
> <xjc package="org.foo.bar">
> <schema dir="src/main/schemas" includes="**/*.xsd" />
> </xjc>
> <!--
> if you need multiple compilations
> you can specify them separately as <xjc> elements.
> -->
> </configuration>
>
>
> > I agree with Kohsuke that some of the users will already have ant build
> > files, and that for them it will be easier to use that format...
> However, I
> > agree with you that as a Maven2 project it seems like Maven2 style is
> most
> > appropriate. I'd personally rather not use any Ant syntax in my build
> -- I
> > switched to maven for a reason :)
>
> So I'd like to better understand which aspect of the above syntax is so
> "Ant-like" that Maven folks won't like it.
>
>