You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cxf.apache.org by Jim Ma <ji...@iona.com> on 2007/03/14 11:41:49 UTC
question about xsdtojava jaxb maven plugin
Hi all ,
Does anyone have any idea why this is happening ?
If we removed the following dependency (marked with ====)from metacode
module,
buid rt-management always failed.
<plugin>
<groupId>org.apache.cxf</groupId>
<artifactId>cxf-common-xsd</artifactId>
<version>${project.version}</version>
<executions>
<execution>
...
</configuration>
<goals>
<goal>xsdtojava</goal>
</goals>
</execution>
</executions>
<dependencies>
=========================
<dependency>
<groupId>org.apache.cxf</groupId>
<artifactId>cxf-tools2-xjc-dv</artifactId>
<version>${project.version}</version>
</dependency>
=========================
<dependency>
<groupId>org.apache.cxf</groupId>
<artifactId>cxf-common-utilities</artifactId>
<version>${project.version}</version>
</dependency>
</dependencies>
</plugin>
rt-management always complain unrecognized parameter -Xdv. But I have set
the
the cxf-tools-xjc-dv dependency for xsdtojava plugin . Is this an issue in
our jaxb plugin ?
Another question is : Why do we need to implement our own jaxb plugin
instead of using Sun's jaxb plugin ?
Thanks
Jim
Re: question about xsdtojava jaxb maven plugin
Posted by James Mao <ja...@iona.com>.
Hi
I just put dependency of the xjc plugin in metacode, since it's the on
top of api/rt, although metacode never use the xjc plugin.
but seems that's the only workaround solution i can figure out.
James.
> Hi Jim,
>
> I have come accross a similar (or the same) problem a while ago: the
> first time a code-generator was run it had to already have all the
> dependencies for subsequent runs declared - this was causing problems
> with testing extensions that were only built as part of the CXF
> project (i.e. the default value plugin, and former cfg plugin) and the
> reason Sun's maven-jaxb-plugin was used for testing them.
> I believe this is a bug in maven.
>
> Andrea.
>
> Jim Ma wrote:
>
>> Hi all ,
>>
>> Does anyone have any idea why this is happening ?
>>
>> If we removed the following dependency (marked with ====)from
>> metacode
>> module,
>> buid rt-management always failed.
>>
>> <plugin>
>> <groupId>org.apache.cxf</groupId>
>> <artifactId>cxf-common-xsd</artifactId>
>> <version>${project.version}</version>
>> <executions>
>> <execution>
>> ...
>> </configuration>
>> <goals>
>> <goal>xsdtojava</goal>
>> </goals>
>> </execution>
>> </executions>
>> <dependencies>
>> =========================
>> <dependency>
>> <groupId>org.apache.cxf</groupId>
>> <artifactId>cxf-tools2-xjc-dv</artifactId>
>> <version>${project.version}</version>
>> </dependency>
>> =========================
>> <dependency>
>> <groupId>org.apache.cxf</groupId>
>> <artifactId>cxf-common-utilities</artifactId>
>> <version>${project.version}</version>
>> </dependency>
>> </dependencies>
>> </plugin>
>>
>> rt-management always complain unrecognized parameter -Xdv. But I
>> have set
>> the
>> the cxf-tools-xjc-dv dependency for xsdtojava plugin . Is this an
>> issue in
>> our jaxb plugin ?
>>
>> Another question is : Why do we need to implement our own jaxb plugin
>> instead of using Sun's jaxb plugin ?
>>
>> Thanks
>>
>> Jim
>>
>>
>>
>
>
Re: question about xsdtojava jaxb maven plugin
Posted by Andrea Smyth <an...@iona.com>.
Hi Jim,
I have come accross a similar (or the same) problem a while ago: the
first time a code-generator was run it had to already have all the
dependencies for subsequent runs declared - this was causing problems
with testing extensions that were only built as part of the CXF project
(i.e. the default value plugin, and former cfg plugin) and the reason
Sun's maven-jaxb-plugin was used for testing them.
I believe this is a bug in maven.
Andrea.
Jim Ma wrote:
>Hi all ,
>
>Does anyone have any idea why this is happening ?
>
> If we removed the following dependency (marked with ====)from metacode
>module,
>buid rt-management always failed.
>
><plugin>
> <groupId>org.apache.cxf</groupId>
> <artifactId>cxf-common-xsd</artifactId>
> <version>${project.version}</version>
> <executions>
> <execution>
> ...
> </configuration>
> <goals>
> <goal>xsdtojava</goal>
> </goals>
> </execution>
> </executions>
> <dependencies>
> =========================
> <dependency>
> <groupId>org.apache.cxf</groupId>
> <artifactId>cxf-tools2-xjc-dv</artifactId>
> <version>${project.version}</version>
> </dependency>
> =========================
> <dependency>
> <groupId>org.apache.cxf</groupId>
> <artifactId>cxf-common-utilities</artifactId>
> <version>${project.version}</version>
> </dependency>
> </dependencies>
> </plugin>
>
>rt-management always complain unrecognized parameter -Xdv. But I have set
>the
>the cxf-tools-xjc-dv dependency for xsdtojava plugin . Is this an issue in
>our jaxb plugin ?
>
>Another question is : Why do we need to implement our own jaxb plugin
>instead of using Sun's jaxb plugin ?
>
>Thanks
>
>Jim
>
>
>