Issue compiling model with 3.0.5 on Windows

[Oleg Cohen]

We just upgraded to use 3.0.5 and started getting an error when compiling the model:

[ERROR] Failed to execute goal org.sculptorgenerator:sculptor-maven-plugin:3.0.5:generate (code-generation) on project XXXXXX: Execution code-generation of goal org.sculptorgenerator:sculptor-maven-plugin:3.0.5:generate failed: Cannot create a resource for 'c:\Users\*********\src\main\resources\model.btdesign'; a registered resource factory is needed -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.sculptorgenerator:sculptor-maven-plugin:3.0.5:generate (code-generation) on project XXXXXX: Execution code-generation of goal org.sculptorgenerator:sculptor-maven-plugin:3.0.5:generate failed: Cannot create a resource for 'c:\Users\*********\\src\main\resources\model.btdesign'; a registered resource factory is needed

Here is the stacktrace:

org.eclipse.xtext.resource.SynchronizedXtextResourceSet.getResource(SynchronizedXtextResourceSet.java:24)
    at org.sculptor.generator.workflow.SculptorGeneratorWorkflow.readModel(SculptorGeneratorWorkflow.java:181)
    at org.sculptor.generator.workflow.SculptorGeneratorWorkflow.run(SculptorGeneratorWorkflow.java:106)
    at org.sculptor.generator.SculptorGeneratorRunner.run(SculptorGeneratorRunner.java:48)
    at org.sculptor.maven.plugin.GeneratorMojo.doRunGenerator(GeneratorMojo.java:474)
    at org.sculptor.maven.plugin.GeneratorMojo.executeGenerator(GeneratorMojo.java:439)
    at org.sculptor.maven.plugin.GeneratorMojo.execute(GeneratorMojo.java:223)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:106)
    ... 21 more

This used to work fine with 3.0.4 and works ok on Mac. It appears to be a Windows-specific issue where the full path has c:\ in it.

Would appreciate help with a fix or a workaround!!!

Regards,
Oleg

[Torsten Juergeleit]

This issue is a regression of #39 (we have a lack of tests on Windows - Travis CI is Linux-only) and tracked in #148. The only workaround is using the Maven plugin from version to 3.0.4.

I'll come up with a hotfix release.

/Torsten

[Torsten Juergeleit]

The hotfix release 3.0.6 is available on Maven Central.

/Torsten