Exclude schemas configuration strangeness

From: William Simons <william.simons_at_childrens.harvard.edu>
Date: Fri, 21 Apr 2006 14:25:52 -0400

Here's some strange behavior that I'm seeing using the JAXB2 Maven2
plugin... I'm not even sure that its related to the plugin so I didn't put
that in the subject.

A number of my schemas import other schemas that are part of the same
compile. When I run my builds on OSX and Linux using the following
configuration everything works great:

        <configuration>
          <extension>true</extension>
          <catalog>src/main/resources/catalog.cat</catalog>
        </configuration>

However, when I run the build on XP pro using the command prompt or using
cygwin, I get a number of errors like:

[ERROR] 'OSStoreServerConfigType' is already defined...

In maven 1 and ant I solved this using by excluding the schemas that were
imported. So I tried with a new configuration:

        <configuration>
          <extension>true</extension>
          <catalog>src/main/resources/catalog.cat</catalog>
          <excludeSchemas>
            <excludeSchema>**/config.xsd</excludeSchema>
            <excludeSchema>**/responderInit.xsd</excludeSchema>
            <excludeSchema>**/attributes.xsd</excludeSchema>
            <excludeSchema>**/credentials.xsd</excludeSchema>
            <excludeSchema>**/pid.xsd</excludeSchema>
          </excludeSchemas>
        </configuration>

And now it works in both. I assume that the latter is the correct behavior
but I think that its strange that it behaves differently in Windows than in
OSX/Linux.

Anyone else seen this problem or anything similar between the two
environments?

Thanks,
Bill