Google Git
Sign in
eclipse / sapphire / org.eclipse.sapphire / refs/tags/R-9.0.3
tag7319d305d6c4b89536c591f21d65e3b2d1a5cdec
taggerKonstantin Komissarchik <konstantin.komissarchik@oracle.com>Mon Nov 02 06:08:06 2015 -0800
object7cceeb6cc341345f8fec81ea123d00e345ff6bf6 
Release 9.0.3
commit7cceeb6cc341345f8fec81ea123d00e345ff6bf6[log] [tgz]
authorDanny Ju <danny.ju@oracle.com>Fri Oct 23 11:42:56 2015 -0700
committerKonstantin Komissarchik <konstantin.komissarchik@oracle.com>Fri Oct 23 14:55:09 2015 -0700
tree6aafdc32ee6b9eae6165196b5bc3186076ed5385
parent52da2e8410e2e3b53f3e2502f861b8c707a09b07 [diff]
Fix : DelayedTasksExecutor does not restart after shutdown

The worker thread of the DelayedTasksExecutor is designed to shutdown
after ten minutes of no activity. It is supposed to restart when a new
task is submitted, but upon the restart, the thread immediately shuts
down again. This causes property changes entered in the UI to not make
it to the model, which in turn causes validation (among other aspects)
to not be updated.

The fault lies in not resetting timeOfLastWork prior to restarting the
worker thread.

Bugzilla: https://bugs.eclipse.org/bugs/show_bug.cgi?id=480468
Signed-off-by: Danny Ju <danny.ju@oracle.com>
1 file changed
tree: 6aafdc32ee6b9eae6165196b5bc3186076ed5385
  1. .gitignore
  2. .project
  3. README.md
  4. build.properties
  5. build.xml
  6. features/
  7. findbugs-excludes.xml
  8. plugins/
  9. releng/
README.md

Introduction

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.

More Information

License

Eclipse Public License (EPL)

Releases

Information on past and future releases along with the downloads can be found on the releases page.

Discussion

Questions should be directed to the adopter forum.

Bugzilla

This project uses Bugzilla to track issues and enhancement requests.

Installing

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).

Releases

Building

The build is easy to run on a local machine.

  1. Make sure that you have JDK 6 and Ant installed. Both should be on the path.
  2. Set JDK_16_HOME environment variable to point to your JDK 6 install.
  3. Clone the Sapphire Git repository and pick the desired branch.
  4. Open a shell to the Git workspace and execute ant clean-start.

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.

Example: 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.

Example: ant clean-start -Ddownloads=d:/sapphire/downloads

Once the build completes, you will notice the following key folders in the Git workspace:

  • build/repository : Repository of build artifacts, including runtime bundles, source bundles and the SDK.
  • dev-eclipse : Eclipse with select plugins along with Sapphire SDK from the build. This Eclipse configuration is designed to be appropriate for working on Sapphire.
  • dev-target : Eclipse with select plugins along with all of Sapphire, including source bundles. This Eclipse configuration is designed to make a good target platform.

Contributing

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.

Note that before your contribution can be accepted, you need to complete the Contributor License Agreement (CLA). See FAQ for more information.