In theory, we could set it up so that they could use either format fairly
easy....
What if we did a Java MOJO that had all the XJC configuration settings as
options -AND- had an optional <xjcTask>xjc-build.xml</xjcTask>
The only difficulty would be in ensuring that the XJCMojo adds any new
XJCTask configurations...
Malachi
On 3/1/06, Malachi de Ælfweald <malachid_at_gmail.com> wrote:
>
>
> On 3/1/06, Jonathan Johnson <jonjohnson_at_mail.com> wrote:
>
> > <plugin>
> > <groupId>com.sun.tools.xjc.maven2 </groupId>
> > <artifactId>maven-jaxb-plugin</artifactId>
> > <executions>...</executions>
> > <configuration>
> > <xjc ant task definition here />
> > </configuration>
> >
> > ... instead of defining its own syntax for the maven plugin. I plan to
> > > look at the code to see how hard it is to do this, and hopefully I
> > > should be able to submit a patch for a consideration of Jonathan.
> >
> > The configuration instructions I sent in my announcement email are not
> > written in stone. They are a starting point for us to decide on the best
> > configuration interface. Using the ant xjc configuration is not out of the
> > question and there are definite merits. Two technical roadblocks are
> > 1) Maven does not make it obvious on how to get the raw configuration
> > block. (Their documentation just talks about mapped configuration to the
> > plugin java objects, but I'm sure there is a way) 2) XJC2Task does not have
> > a method to submit the xml configuration section.
> >
>
>