| commit | 37c69ab7a042f470d792156adf2ba7076b700a16 | [log] [tgz] |
|---|---|---|
| author | Bernd Hufmann <Bernd.Hufmann@ericsson.com> | Fri Nov 27 15:25:11 2015 -0500 |
| committer | Alexandre Montplaisir <alexmonthy@efficios.com> | Sat Nov 28 17:44:05 2015 -0500 |
| tree | 9cf147edc21ce492888425c0a3d0ce0161ed69f6 | |
| parent | 7c8592b46137c929552484888c48f3fb3b7e0a2e [diff] |
Restore "Add test traces for memory usage view" This restores commit 6507725dd124a32a3c76b67cfa61a3775e2da94d (and reverts 784762fc53bf18ec40d0d7269545a4a72070c6a2). The standard jobs now always deploys to latest/, and we can copy the contents in separate directories to make them available in the composite repo. Signed-off-by: Alexandre Montplaisir <alexmonthy@efficios.com>
This tree contains a set of CTF test traces, primarily for use in Trace Compass.
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.
The modules follow the Maven standard directory layout.
To add a new CTF test trace, add it to the ctf/src/main/resources directory. Make sure it is not archived or anything, as this will be exposed as-is to the users.
Then update the ctf/src/main/java/.../CtfTestTrace.java file accordingly to include the new trace.
Finally, bump the project's minor version (1.1 -> 1.2) in the main pom.xml and related <parent> blocks.