A plan for migrating WebDSL to git and github. We want to keep the source history, but also remove the binaries from it to keep the size manageable. The editor project should be integrated to avoid mismatches between editor and compiler versions.

migration plan

  • Convert whole compiler and editor project history including binaries (primarily jars and old template tar) to a webdsl-legacy project.
  • Create a new webdsl project that imports the history of the compiler and editor source files, but excludes the binaries. Put the editor projects (editor, feature, updatesite) in “editor” directory.
  • Create a submodule with the current jars, ignore the history as it can be retrieved from the legacy project.

further improvements

Further possible changes after migration (will probably become more clear once we’ve migrated and started using it):

  • Use Maven for jar dependencies instead of a submodule.
  • Move standard library to a submodule. Add compiler option to let user compile with own checkout of the library.
  • Change project structure of compiler and editor, e.g. use submodules as well. Currently the editor can import from a webdsl install dir, but it would be nice to just have one build action. This also depends on how Spoofax evolves.
Submitted by Danny Groenewegen on 18 November 2013 at 15:08

On 18 November 2013 at 15:48 Elmer van Chastelet commented:

I’m ok with this. My only concern is the merging of editor projects into the compiler repo, not sure if these projects are easy to work with when they are part of the compiler project/repo.

Log in to post comments