|author||Matthew Khouzam <email@example.com>||Thu Dec 15 10:46:31 2016 -0500|
|committer||Matthew Khouzam <firstname.lastname@example.org>||Mon Dec 19 12:58:48 2016 -0500|
tmf.ui: Gracefully handle invalid tar import operations A tar.gz file may have an invalid tar file in the gzip. The getNextEntry would return null in such a case. This performs that null check in order to validate the tar and avoid a user- facing NPE. Change-Id: I28ae7c787d77a0f1c9136264cfc678d7e52cda1a Signed-off-by: Matthew Khouzam <email@example.com> Reviewed-on: https://git.eclipse.org/r/87247 Reviewed-by: Hudson CI Reviewed-by: Marc-André Laperle <firstname.lastname@example.org> Tested-by: Marc-André Laperle <email@example.com> (cherry picked from commit 6facaeb6ec0e729c457abb780fbc05995c0061cd) Reviewed-on: https://git.eclipse.org/r/87272
This source tree contains the source code for the Trace Compass plugins for Eclipse.
The plugins are categorized as follows:
analysis/ | Generic extensions to the base framework btf/ | Best Trace Format (BTF) integration common/ | Generic utilities that can be used by other plugins ctf/ | Common Trace Format (CTF) reader library doc/ | Documentation and code examples gdbtrace/ | Support for reading and viewing GDB traces lttng/ | LTTng integration pcap/ | libpcap integration rcp/ | Code specific to the RCP version releng/ | Releng-related plugins statesystem/ | State System library tmf/ | Core framework
components.svg file for a diagram showing the dependencies between the different components.
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
The Maven project build requires version 3.3 or later. It can be downloaded from http://maven.apache.org or from the package management system of your distro.
To build the project 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
Stand-alone application (RCP) packages will be placed in
The p2 update site, used for installation as plugins inside Eclipse, will be placed in
The following Maven profiles and properties are defined in the build system. You can set them by using
-P[profile name] and
-D[property name]=[value] in
Defines which target to use. This is used to build against various versions of the Eclipse platform. Available ones are in
releng/org.eclipse.tracecompass.target. The default is usually the latest stable platform. To use the staging target for example, use
Re-compiles the CTF grammar files. This should be enabled if you modify the
.g files in the
Disables the “build-rcp” profile to skip building the RCP archives.
Runs a test suite present in
releng/org.eclipse.tracecompass.alltests. The test suite to run has to be defined by
-DcustomTestSuite=[name], for example
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).