Lennart Jörelid

CDI Producer methods provide a generic way of creating Emitters. Some implications of this: - The `EmitterFactoryFor` annotation seems introduced to enable separate specification types for Emitters as illustrated in...

Fixes #MCHECKSTYLE-287 Fixes #MCHECHSTYLE-294

Hello there, Handle them separately is fine; I was simply lazy enough to continue developing in the same repo. I realized that the same root cause has been the origin...

Could be the effect of using "\" which is being interpreted as an escape char. Will move to ant patterns instead; the Java Regexps cause confusion.

I believe this is indeed an enhancement request for the plugin to support something it currently does not, namely having sources reside outside of the project as indicated by the...

That is, indeed, the Maven Way (tm) - and for good reason. The standard approach is: 1. If you need some resource or plugin to build the current project, include...

It seems that the problem is the naming of your project, which contains a space, which - in turn - gets converted into an escaped "%20" char. I would recommend...

We normally use xsd:import, rather than xsd:include within the ITs. Will device an integration test for import as well. However, in the meantime you could use the import statement instead.

Could you create an integration test for this issue, and send as a PR?

The semantics are slightly different in the 2.x JAXB version. Use relative path to the file where the XSD was included: ```xml ```