http://mojo.codehaus.org/jaxb2-maven-plugin/source-repository.html

But it's better to use trunk instead of the tag.

/Anders


On Mon, May 27, 2013 at 5:33 PM, Miguel Garz <miguel.g...@gmail.com> wrote:

> Hi people,
> I'm actually looking into the plugin code, and I think I might fix it.
> Is it a possibility to download the source code and build the plugin
> locally?
> Any help?
> Thanks,
> Miguel Garz
>
>
> On Mon, May 27, 2013 at 3:07 PM, Miguel Garz <miguel.g...@gmail.com>wrote:
>
>> Good morning/afternoon everybody.
>> I'm having some problem with the mojo-Jaxb plugin.
>> What's happening is that I configured the plugin to output the schemas to
>> a specific folder,
>> that works fine, unless I use the <transformSchemas> tag to configure the
>> schema name.
>> In this case, what happens is that the schemas are generated, without the
>> correct name, but in the standard folder (not the one in the
>> <outputDirectory>).
>> Below is my maven pom configuration and also a excerpt of my code (with
>> the annotations),
>> Would someone know what I'm doing wrong or if it is a bug on the plugin?
>> Thanks,
>> Miguel Garz
>>
>> My pom:
>>
>> <plugin>
>> <groupId>org.codehaus.mojo</groupId>
>>  <artifactId>jaxb2-maven-plugin</artifactId>
>> <version>1.5</version>
>> <executions>
>>  <execution>
>> <phase>generate-resources</phase>
>> <id>schemagen</id>
>>  <goals>
>> <goal>schemagen</goal>
>> </goals>
>>  <configuration>
>> <verbose>true</verbose>
>> <transformSchemas>
>>  <transformSchema>
>> <uri>http://delagelanden.com/rijee6/ws-domain</uri>
>>  <toPrefix>rid</toPrefix>
>> <toFile>ri6-ws-domain</toFile>
>> </transformSchema>
>>  </transformSchemas>
>> <includes>
>> <include>com/delagelanden/rijee6/domain/*.java</include>
>>  </includes>
>> <outputDirectory>${basedir}/../schema/src/main/xsd</outputDirectory>
>>  </configuration>
>> </execution>
>> </executions>
>>  </plugin>
>>
>>
>> My classes:
>>
>> ...
>> @XmlType(namespace="http://delagelanden.com/rijee6/ws-domain"; )
>> public class Project {
>> ...
>>
>>
>>
>

Reply via email to