|tagger||Konstantin Komissarchik <email@example.com>||Fri Oct 16 21:05:53 2015 -0700|
|author||Konstantin Komissarchik <firstname.lastname@example.org>||Thu Oct 15 13:38:14 2015 -0700|
|committer||Konstantin Komissarchik <email@example.com>||Thu Oct 15 13:38:14 2015 -0700|
Releng : Remove MaxPermSize usage since Java 8 does not need this
Sapphire is a user interface development framework that improves productivity. Instead of focusing on individual widgets, layouts and data binding, the developers focus on modeling the semantics of the data and declaring the general intent of how the data it to be presented.
Information on past and future releases along with the downloads can be found on the releases page.
Questions should be directed to the adopter forum.
This project uses Bugzilla to track issues and enhancement requests.
Sapphire is distributed as a p2 repository, from which the various components can be installed. Every release page either lists the URL of the repository (for finished releases) or includes a link to a Hudson build job (for in-progress releases).
The build is easy to run on a local machine.
JDK_16_HOMEenvironment variable to point to your JDK 6 install.
The build must be able to pull dependencies from the eclipse.org downloads server and its mirrors. If you are behind a proxy, you will need to invoke build with proxy configuration. If the proxy is properly configured at the operating system level, you should only need to add
-autoproxy switch to the build command.
ant clean-start -autoproxy
If you are working with multiple Sapphire branches, you may want to share the downloads directory so that every branch does not need to re-download everything it needs. The default downloads folder is
[root]/downloads, but you can change it by setting the
SAPPHIRE_DOWNLOADS environment variable or the
downloads property when invoking the build. An absolute path is required in both cases.
ant clean-start -Ddownloads=d:/sapphire/downloads
Once the build completes, you will notice the following key folders in the Git workspace:
Contributions to this project are always welcome as a Bugzilla attachment of a patch. This project currently does not accept contributions through Gerrit or through GitHub pull requests.