This repository contains contains a set of CTF and Ftrace test traces, primarily for use in Trace Compass. They are intented to be used for implementing automated tests, such as JUnit tests.

To build the package and install it in your local Maven repo, simply isssue

mvn clean install

You can also use the deploy target to populate both a standard Maven repo and a p2 update site. The -Dmaven-deploy-destination and -Dp2-deploy-destination properties can be used to specify their respective deploy locations. For example:

mvn clean deploy -Dmaven-deploy-destination=file:///var/www/traces/maven -Dp2-deploy-destination=/var/www/traces/repository

(Note that the first property needs a file:/// scheme, but the second does not.)

You can then point depending projects to these locations.

By default a snapshot version is built and deployed. To deploy a release version for the Maven repo, the pom.xml files need to be updated to remove the SNAPSHOT tag from pom.xml files. This is not needed when deploying p2 update sites.

Read our contributor guide and follow the instructions to contribute code.

When contributing a new test trace, please make sure that it only contains content that you are allowed to share in open source.

As opposed to the previous Eclipse CI infrastructure setup, the new setup doesn't have direct write access to the deployment server, and hence the Maven repo and p2 update site cannot be copied directly.

The Release Jenkins Job is now configured to deploy the artificats to the deployment server. A committer in the Eclipse Trace Compass project can trigger this build manually to make a release. After the release is done tag the version with the new version tag, for example 1.8.0.

• p2 update site (for use in Eclipse .target files). Replace 1.8.0 with your required version.
  • http://archive.eclipse.org/tracecompass/tracecompass-test-traces/repository/latest/
  • http://archive.eclipse.org/tracecompass/tracecompass-test-traces/repository/1.8.0/
• Standard Maven repo (for use in Maven <dependency> blocks)
  • http://archive.eclipse.org/tracecompass/tracecompass-test-traces/maven/

The Nighly Jenkins Job is configured to deploy a nighly p2 updates site which is automatically triggered when the source code repository is updated.

• p2 update site (for use in Eclipse .target files)
  • http://archive.eclipse.org/tracecompass/tracecompass-test-traces/repository/nightly/

Note: Starting with version 1.8.0 only p2 update sites are maintained and the Maven repo is not deployed anymore.