Yes, sorry, must have been C-inking ;-)
On Wed, Nov 12, 2008 at 2:16 PM, Lulseged Zerfu <lulseged.zerfu_at_ericsson.com
> wrote:
> Thanks
>
> Do you mean import when you mean <include>?
>
> Lulseged
>
> ------------------------------
> *From:* Wolfgang Laun [mailto:wolfgang.laun_at_gmail.com]
> *Sent:* den 11 november 2008 16:26
> *To:* users_at_jaxb.dev.java.net
> *Subject:* Re: schemaExcluds
>
> If one of the .xsd files that are not excluded would contain an <include>
> with one of those two .xsd files, then the Java classes for them would be
> generated anyway.
> -W
>
> On Tue, Nov 11, 2008 at 3:15 PM, Lulseged Zerfu <
> lulseged.zerfu_at_ericsson.com> wrote:
>
>> Hi
>>
>> I don't know if I have to post this here. If it is not the right place to
>> post, please let me know.
>>
>> I am using maven-jaxb-plugin. It works fine but the schemaExcludes
>> configuration has no effect.
>>
>> Here is how it looks like:
>>
>> <
>> schemaLanguage>AUTODETECT</schemaLanguage>
>> <bindingDirectory>src/main/resources/schema</bindingDirectory>
>> <bindingIncludes>
>> <include>*.xjb</include>
>> </bindingIncludes>
>>
>> <schemaDirectory>src/main/resources/schema</schemaDirectory>
>> <schemaIncludes>
>> <include>*.xsd</include>
>> </schemaIncludes>
>>
>> <schemaExcludes>
>> <exclude>urn.ietf.params.xml.ns.common-policy.xsd</exclude>
>> <exclude>urn.ietf.params.xml.ns.pres-rules.xsd</exclude>
>> </schemaExcludes>
>>
>> The schemas that are supposed to be excluded (in this case 2) are
>> generated anyway.
>>
>> Why?
>>
>> Lulseged
>>
>
>