Where is the class documented, I have not heard of this problem? On 22 December 2015 at 12:07, Joerg Schoenfisch < [email protected]> wrote:
> So, apparently there is some code in the method setGlobalReplacements() in > the schemagen class that should prevent this error. However, it does not > seem to work. > > I tried to do some debugging, but when cloning the repository and > importing the Maven projects in Eclipse I get a lot of errors because of > references to the missing import org.apache.jena.ext > > Any hints on how to resolve that missing import? Should I report that > Windows problem as a bug? > > > Best > > > > > On 16.12.2015 18:27, Joerg Schoenfisch wrote: > >> Hi everybody, >> >> I'm trying to generate some Java files with schemagen 3.0.1 on Windows. >> Unfortunately, schemagen includes the full path to the file in the >> JavaDoc, including backslashes, e.g "D:\Documents\uni[...]". This >> results in a compilation error because of an illegal unicode escape. >> >> Furthermore, when I try to change the file header in the POM >> configuration a BadBooleanException is thrown (only seen when running >> Maven in debug. Standard error message is quite bad). >> The relevant configuration looks like this: >> >> <fileOptions> >> <source> >> <input>default</input> >> <header>foobar</header> >> </source> >> </fileOptions> >> >> Is there any way to work around this? Am I using the configuration in >> Maven wrong? >> >> >> Best >> >> -- Jonathan Camilleri Mobile (MT): ++356 7982 7113 E-mail: [email protected] Please consider your environmental responsibility before printing this e-mail. I usually reply to emails within 2 business days. If it's urgent, give me a call.
