|author||Bernd Hufmann <Bernd.Hufmann@ericsson.com>||Thu Apr 23 14:13:49 2015 -0400|
|committer||Bernd Hufmann <firstname.lastname@example.org>||Fri Apr 24 10:37:58 2015 -0400|
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 <email@example.com> Tested-by: Matthew Khouzam <firstname.lastname@example.org> Reviewed-on: https://git.eclipse.org/r/46428 Tested-by: Bernd Hufmann <email@example.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
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 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 clean install -Pbuild-rcp -Dmaven.test.skip=true
This will build the RCP for all supported architectures. The resulting archives will be placed in
These commands will also build the p2 update site, which will be placed in
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
Re-compiles the CTF grammar files. This should be enabled if you modify the
.g files in the
Builds the RCP archives. Refer to the previous section for details.
Mainly for use on build servers. Copies the generated RCP archives, as well as the RCP-specific update site, to the paths specified by
-DrcpSiteDestination=/absolute/path/to/destination, respectively. Must be used with
Mainly for use on build servers. Copies the standard update site (for the Eclipse plugin installation) to the destination specified by
Mainly for use on build servers. Signs all the generated update sites using the Eclipse signing server.
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).