The production of the strategoxt.jar still involves a step employing the C-based Stratego compiler. This should be replaced by a purely Java-based process. This can then also simplify the build process for Stratego/XT.

Submitted by Eelco Visser on 9 January 2013 at 22:08

On 9 January 2013 at 22:08 Eelco Visser tagged 1.3

On 9 January 2013 at 22:09 Eelco Visser commented:

Marked for 1.3, but perhaps we can already integrate the new Stratego/XT jar in release 1.1.


On 9 January 2013 at 22:09 Eelco Visser tagged @vvergu

On 14 January 2013 at 20:15 Vlad Vergu tagged 1.1

On 14 January 2013 at 20:15 Vlad Vergu removed tag 1.3

On 18 January 2013 at 20:11 Guido Wachsmuth commented:

Is this required for 1.1?


On 30 January 2013 at 12:52 Vlad Vergu commented:

It is bootstrapped now. Should we include it in the nightly build of Spoofax? Also in release 1.1?


On 30 January 2013 at 12:52 Vlad Vergu commented:

-duplicate comment-


On 30 January 2013 at 12:53 Vlad Vergu commented:

Moving to 1.2 because of a clear need for testing this before release. Should be included in unstable immediately after release 1.1.


On 30 January 2013 at 12:53 Vlad Vergu tagged 1.2

On 30 January 2013 at 12:53 Vlad Vergu removed tag 1.1

On 30 January 2013 at 12:54 Vlad Vergu tagged improvement

On 8 February 2013 at 19:24 Vlad Vergu commented:

Ok, so here’s an update:

  • We can now bootstrap
  • The branch is built automatically Hydra now
  • The compiler tests that exist need to be hooked in the build process and executed
  • Java-front needs to be pulled in in the repo. That will make the project self-contained
  • The codebase needs to be cleaned up and obsolete things should be moved out/removed.
  • The result needs to be included in Spoofax nightly asap so we can get some real testing before next release

On 28 July 2014 at 22:48 Gabriël Konat closed this issue.

Log in to post comments