Skip to content
This repository has been archived by the owner on Mar 27, 2018. It is now read-only.

Latest commit

 

History

History
46 lines (27 loc) · 3.12 KB

README.md

File metadata and controls

46 lines (27 loc) · 3.12 KB
Raw

This repository is now closed and has been replaced with https://github.com/eclipse/scanning which is the open source project to which the repository has been moved.

This repository now exists to hold the projects which weren't moved to https://github.com/eclipse/scanning and hold the history of files.

To use git replace to import this history into your current eclipse scanning repository:

cd scanning.git
git remote add project-history git://github.com/DiamondLightSource/daq-eclipse.git
git fetch project-history
git replace -g 712c0bb1fa039a203c7187240affa4ae3ddebedf f76df577dc007570d9309aadf48eaf480daf851b

To reverse this, simply delete the replace spec:

git replace -d 712c0bb1fa039a203c7187240affa4ae3ddebedf

daq-eclipse

Build Status

The purpose of this repository is to hold open source code before it is submitted into an Eclipse Project.

This repository is checked by a Travis CI build which looks at the last commit message.

It is compulsory to reference a jira commit or merge from a commit that does or the build will fail.

Adding Tests

The test system is linked into Travis CI and your pull request will be checked with the build and test. Tests should not be added in the same bundle that created the feature but in a .test bundle which may be a fragment of the original bundle. This enables the build to remove test code from the binary easily because those bundles are not in the feature. NOTE This has the added benefit that your test bunles or fragment may have dependencies which the main bundle does not. For instance in org.eclipse.scanning.test we depend on almost eveything imaginable but of course this bundle is not part of the binary product.

Instead of having to name your class *Test as in other projects, in this project you should add a Suite to each package of tests. This defines the tests that are run automatically in the build. This procedure allows for long running or CPU/threading tests to be ommited from a build to keep the run time down while waiting for the merge.

Example: org.eclipse.scanning.test.points.Suite

Check out a development version

  1. Clone repositories as specified in .travis.yml at the top of this repository (richbeans, dawnsci, dawn-hdf)
  2. Clone this repositiory to org.eclipse.scanning
  3. Import all the bundles from all the repos to your eclipse workspace (other IDE's are available but they probably don't support target platforms)
  4. Use the org.eclipse.scanning.target.platform target plaform which will pull in a few apacahe dependencies
  5. After setting this target as the target platform, your code should compile
  6. Start an apachemq on localhost:61616
  7. Run the example server and example client and go to the 'X-Ray Centering' example erspective or the 'Scanning' perspective.