|author||Alexandre Montplaisir <firstname.lastname@example.org>||Fri Jun 09 18:26:47 2017 -0400|
|committer||Alexandre Montplaisir <email@example.com>||Fri Jun 09 18:30:25 2017 -0400|
Add a trace to test stream intersection Bump version to 1.7.0. Signed-off-by: Alexandre Montplaisir <firstname.lastname@example.org>
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
-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.
Make sure the parameters (event count, etc.) are correct! This project does not check those at the moment, but if they are incorrect they will fail some Trace Compass unit tests. This is a known issue.
Finally, bump the project's minor version (1.1.0 -> 1.2.0) in the main pom.xml and related
mvn deploy goal, when run from the Eclipse CI servers, will deploy to the following locations:
When pushing a new version, some extra work is required on the server to update the p2 update site. The
/repository/ is directory a actually a p2 composite repository. But since the deploy simply overwrites the contents of
/repository/latest/, you need to do the following steps manually:
/latest/directory to a new directory named after the new version, like
/1.2.0/(copy not move, please keep
compositeContent.xmlfiles to point to the new directory. Do not delete existing entries, other projects or git branches may still be using those.
No extra steps are required for the Maven repo, since the Maven plugin handles multi-version deploying automatically.