| commit | c3baa0dbc483ddcd9b6c8433d20746742afa7379 | [log] [tgz] |
|---|---|---|
| author | Bernd Hufmann <Bernd.Hufmann@ericsson.com> | Thu Apr 23 14:13:49 2015 -0400 |
| committer | Bernd Hufmann <bernd.hufmann@ericsson.com> | Fri Apr 24 10:37:58 2015 -0400 |
| tree | 91650ea88c3945305d458841ff5525897eba4efa | |
| parent | a92b0ea78b73b65af9a4ad4c80a320e03d70ddb1 [diff] |
ctf: disable failing test for newly added trace in ctf-testsuite Disable it till it's fixed. Change-Id: I8d31f54bbe9cb3cf75f2636ac532db04bafc0f28 Signed-off-by: Bernd Hufmann <Bernd.Hufmann@ericsson.com> Reviewed-on: https://git.eclipse.org/r/46376 Reviewed-by: Hudson CI Reviewed-by: Matthew Khouzam <matthew.khouzam@ericsson.com> Tested-by: Matthew Khouzam <matthew.khouzam@ericsson.com> Reviewed-on: https://git.eclipse.org/r/46428 Tested-by: Bernd Hufmann <bernd.hufmann@ericsson.com>
This source tree contains the source code for the Trace Compass plugins for Eclipse.
The plugins are categorized as follows:
org.eclipse.tracecompass.analysis.* | Generic extensions to the base framework org.eclipse.tracecompass.btf.* | Best Trace Format (BTF) integration org.eclipse.tracecompass.ctf.* | Common Trace Format (CTF) reader library org.eclipse.tracecompass.gdbtrace.* | Support for reading and viewing GDB traces org.eclipse.tracecompass.lttng2.* | LTTng 2.x integration org.eclipse.tracecompass.pcap.* | libpcap integration org.eclipse.tracecompass.rcp.* | Code specific to the RCP version org.eclipse.tracecompass.statesystem.* | State System library org.eclipse.tracecompass.tmf.* | Core framework
See the plugins.svg file for a diagram showing the dependencies between the different plugins.
To set up the environment to build Trace Compass from within Eclipse, see this wiki page: http://wiki.eclipse.org/Trace_Compass/Development_Environment_Setup
To build the plugins manually using Maven, simply run the following command from the top-level directory:
mvn clean install
The default command will compile and run the unit tests. Running the tests can take some time, to skip them you can append -Dmaven.test.skip=true to the mvn command:
mvn clean install -Dmaven.test.skip=true
The RCP is not built by default, to build it you need to add -Pbuild-rcp to the mvn command:
mvn clean install -Pbuild-rcp -Dmaven.test.skip=true
This will build the RCP for all supported architectures. The resulting archives will be placed in org.eclipse.tracecompass.rcp.product/target/products.
These commands will also build the p2 update site, which will be placed in org.eclipse.tracecompass.releng-site/target/repository.
The following Maven profiles, and their corresponding properties, are defined in the build system. You can set them by using -P[profile name] and -D[property name]=[value] in mvn commands.
-Pctf-grammar
Re-compiles the CTF grammar files. This should be enabled if you modify the .g files in the ctf.parser plugin.
-Pbuild-rcp
Builds the RCP archives. Refer to the previous section for details.
-Pdeploy-rcp
Mainly for use on build servers. Copies the generated RCP archives, as well as the RCP-specific update site, to the paths specified by -DrcpDestination=/absolute/path/to/destination and -DrcpSiteDestination=/absolute/path/to/destination, respectively. Must be used with -Pbuild-rcp!
-Pdeploy-update-site
Mainly for use on build servers. Copies the standard update site (for the Eclipse plugin installation) to the destination specified by -DsiteDestination=/absolute/path/to/destination.
-Psign-update-site
Mainly for use on build servers. Signs all the generated update sites using the Eclipse signing server.
-Pdeploy-doc
Mainly for use on build servers. Copies the generated HTML documentation to the destination specified by -DdocDestination=/absolute/path/to/destination. Some directories may need to already exist at the destination (or Maven will throw related errors).
