Build using non-staging Eclipse 4.5 target

Since staging will become Eclipse 4.6 (Neon) we should switch to building using
the stable 4.5 target.

Change-Id: I8bcfde64f769510150dc3517b9931521522efdbc
Signed-off-by: Marc-Andre Laperle <marc-andre.laperle@ericsson.com>
Reviewed-on: https://git.eclipse.org/r/50984
Reviewed-by: Hudson CI
Reviewed-on: https://git.eclipse.org/r/51065
3 files changed
tree: 52ecdfd3a057fd0aa994da792acf4e2ec56f3cf7
  1. .gitignore
  2. README.md
  3. TraceCompass.setup
  4. doc/
  5. org.eclipse.tracecompass.alltests/
  6. org.eclipse.tracecompass.analysis.os.linux.core.tests/
  7. org.eclipse.tracecompass.analysis.os.linux.core/
  8. org.eclipse.tracecompass.analysis.os.linux.ui/
  9. org.eclipse.tracecompass.btf.core.tests/
  10. org.eclipse.tracecompass.btf.core/
  11. org.eclipse.tracecompass.btf.ui/
  12. org.eclipse.tracecompass.btf/
  13. org.eclipse.tracecompass.common.core.tests/
  14. org.eclipse.tracecompass.common.core/
  15. org.eclipse.tracecompass.ctf.core.tests/
  16. org.eclipse.tracecompass.ctf.core/
  17. org.eclipse.tracecompass.ctf.parser.tests/
  18. org.eclipse.tracecompass.ctf.parser/
  19. org.eclipse.tracecompass.ctf/
  20. org.eclipse.tracecompass.examples/
  21. org.eclipse.tracecompass.gdbtrace.core.tests/
  22. org.eclipse.tracecompass.gdbtrace.core/
  23. org.eclipse.tracecompass.gdbtrace.ui.tests/
  24. org.eclipse.tracecompass.gdbtrace.ui/
  25. org.eclipse.tracecompass.gdbtrace/
  26. org.eclipse.tracecompass.lttng2.control.core.tests/
  27. org.eclipse.tracecompass.lttng2.control.core/
  28. org.eclipse.tracecompass.lttng2.control.ui.tests/
  29. org.eclipse.tracecompass.lttng2.control.ui/
  30. org.eclipse.tracecompass.lttng2.control/
  31. org.eclipse.tracecompass.lttng2.kernel.core.tests/
  32. org.eclipse.tracecompass.lttng2.kernel.core/
  33. org.eclipse.tracecompass.lttng2.kernel.ui.swtbot.tests/
  34. org.eclipse.tracecompass.lttng2.kernel.ui/
  35. org.eclipse.tracecompass.lttng2.kernel/
  36. org.eclipse.tracecompass.lttng2.ust.core.tests/
  37. org.eclipse.tracecompass.lttng2.ust.core/
  38. org.eclipse.tracecompass.lttng2.ust.ui.tests/
  39. org.eclipse.tracecompass.lttng2.ust.ui/
  40. org.eclipse.tracecompass.lttng2.ust/
  41. org.eclipse.tracecompass.pcap.core.tests/
  42. org.eclipse.tracecompass.pcap.core/
  43. org.eclipse.tracecompass.rcp.branding.feature/
  44. org.eclipse.tracecompass.rcp.branding/
  45. org.eclipse.tracecompass.rcp.product/
  46. org.eclipse.tracecompass.rcp.ui/
  47. org.eclipse.tracecompass.rcp/
  48. org.eclipse.tracecompass.releng-site/
  49. org.eclipse.tracecompass.statesystem.core.tests/
  50. org.eclipse.tracecompass.statesystem.core/
  51. org.eclipse.tracecompass.target/
  52. org.eclipse.tracecompass.testing/
  53. org.eclipse.tracecompass.tmf.analysis.xml.core.tests/
  54. org.eclipse.tracecompass.tmf.analysis.xml.core/
  55. org.eclipse.tracecompass.tmf.analysis.xml.ui.tests/
  56. org.eclipse.tracecompass.tmf.analysis.xml.ui/
  57. org.eclipse.tracecompass.tmf.core.tests/
  58. org.eclipse.tracecompass.tmf.core/
  59. org.eclipse.tracecompass.tmf.ctf.core.tests/
  60. org.eclipse.tracecompass.tmf.ctf.core/
  61. org.eclipse.tracecompass.tmf.ctf.ui.swtbot.tests/
  62. org.eclipse.tracecompass.tmf.ctf/
  63. org.eclipse.tracecompass.tmf.pcap.core.tests/
  64. org.eclipse.tracecompass.tmf.pcap.core/
  65. org.eclipse.tracecompass.tmf.pcap.ui.swtbot.tests/
  66. org.eclipse.tracecompass.tmf.pcap.ui/
  67. org.eclipse.tracecompass.tmf.pcap/
  68. org.eclipse.tracecompass.tmf.remote.core.tests/
  69. org.eclipse.tracecompass.tmf.remote.core/
  70. org.eclipse.tracecompass.tmf.remote.ui.swtbot.tests/
  71. org.eclipse.tracecompass.tmf.remote.ui.tests/
  72. org.eclipse.tracecompass.tmf.remote.ui/
  73. org.eclipse.tracecompass.tmf.remote/
  74. org.eclipse.tracecompass.tmf.ui.swtbot.tests/
  75. org.eclipse.tracecompass.tmf.ui.tests/
  76. org.eclipse.tracecompass.tmf.ui/
  77. org.eclipse.tracecompass.tmf/
  78. plugins.dia
  79. plugins.svg
  80. pom.xml
  81. sync_settings.sh
README.md

Eclipse Trace Compass

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.

Setting up the development environment

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

Compiling manually

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.

Maven profiles and properties

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).