| commit | d4a363337b06caff09ae8e6b3b2843db2472ccfc | [log] [tgz] |
|---|---|---|
| author | Alexandre Montplaisir <alexmonthy@efficios.com> | Fri Nov 27 17:52:26 2015 -0500 |
| committer | Alexandre Montplaisir <alexmonthy@efficios.com> | Fri Nov 27 17:52:26 2015 -0500 |
| tree | 70f2e3132f7758f8d024946fa8a41625d9bb32a1 | |
| parent | 784762fc53bf18ec40d0d7269545a4a72070c6a2 [diff] |
Delete the update-site deploy location before copying the new files Since each "deploy destination" can only contain one given version of the project, might as well clean it before writing. Separate versions could be implemented using a composite repository. 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.