For the SONATA editor we envision an Eclipse or IntelliJ plugin that supports function and service developers. This, however, is our vision on the long run. For now, this repository contains some Java libraries and tools that validate SONATA descriptors using the SONATA schema.
To contribute to the development of the SONATA editor, you may use the very same development workflow as for any other SONATA Github project. That is, you have to fork the repository and create pull requests.
You may contribute to the editor similar to other SONATA (sub-) projects, i.e. by creating pull requests.
The SONATA editor is written in Java and uses the Maven build tool. Thus, you can build the whole editor by typing:
$ mvn clean package
In addition (and because I am a lazy person), there is a Makefile that allows you to build the whole projects, and also sub-projects, like the *-cli and *-web sub-projects, individually.
$ make son-validate-cli
The son-editor relies on some great libraries that have been written before. Below you can find a list of these libraries including their version and license.
- Logback 1.1.3 (EPL 1.0)
- Apache Commons CLI 1.3.1 (Apache 2.0)
- Apache Commons IO 2.4 (Apache 2.0)
- JUnit 4.12 (EPL 1.0)
- Google Guice DI 4.0 (Apache 2.0)
- Guice JUnit Test Runner 1.1 (MIT)
- SnakeYAML 1.16 (Apache 2.0)
- JSON-Java 20160212 (The JSON License)
- JSON-Sanitizer 1.1 (Apache 2.0)
- JSON Schema Validator 1.1.1 (Apache 2.0)
- FasterXML Jackson 2.7.1 (Apache 2.0)
- Spark Core 2.3 (Apache 2.0)
You may find examples on how to use the different tools in the corresponding sub-directories.
The license of the SONATA editor is BSD for now. However, we intend to change it to Apache 2.0 later.
The following lead developers are responsible for this repository and have admin rights. They can, for example, merge pull requests.
- Michael Bredel (mbredel)
Please use the GitHub issues and the SONATA development mailing list email@example.com for feedback.