After upgrading from Spoofax 2.0.0 to Spoofax 2.1.0 I get the following error and I have no idea what this means:

[INFO] Execute strj -i /home/oskar/repos/pgql_lang/pgql-spoofax/trans/pgql_lang.str -o /home/oskar/repos/pgql_lang/pgql-spoofax/src-gen/stratego-java/pgql_lang/trans/ -p pgql_lang.trans --library --clean -I /home/oskar/repos/pgql_lang/pgql-spoofax/src-gen -I /home/oskar/repos/pgql_lang/pgql-spoofax -I /home/oskar/repos/pgql_lang/pgql-spoofax/trans -I /home/oskar/repos/pgql_lang/pgql-spoofax/target/replicate/strj-includes --cache-dir /home/oskar/repos/pgql_lang/pgql-spoofax/target/stratego-cache -la stratego-lib -la stratego-sglr -la stratego-gpp -la stratego-xtc -la stratego-aterm -la stratego-sdf -la strc -la java-front
[INFO] [ strj | error ] No matching subdirectory found in includes for wildcard 'libspoofax/editor/completion/*'!
[INFO] Store get cache hit rate: 0.0%
[INFO] Tree nodes cache hit rate: 0.0%
[INFO] Exodus log cache hit rate: 0.0%
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 01:51 min
[INFO] Finished at: 2017-01-12T16:27:51-08:00
[INFO] Final Memory: 174M/985M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.metaborg:spoofax-maven-plugin:2.1.0:compile (default-compile) on project pgql-lang: BUILD FAILED: MetaborgException -> [Help 1]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1]

I made the following code changes in order to upgrade:

Did I miss anything?

Also when building from Eclipse it doesn't show any more information:

16:48 | ERROR | o.m.s.e.m.b.CompileBuilder     - BUILD FAILED
Submitted by Oskar van Rest on 13 January 2017 at 01:29

On 13 January 2017 at 02:04 Oskar van Rest commented:

it appeared I had to change some dependencies in the yaml file:

On 13 January 2017 at 02:04 Oskar van Rest closed this issue.

On 13 January 2017 at 12:44 Gabriƫl Konat commented:

Right, I forgot to write a migration guide for that. Just added one now:

On 13 January 2017 at 18:52 Oskar van Rest commented:


Log in to post comments