ctf: Avoid direct dependency from the lttng plugins to the ctf.core one

[deliverable/tracecompass.git] / README

diff --git a/README b/README
index 88ebf2355027c82710e73163d65658f6de40c3cd..0a786ea5583e3c5917a831dc4184ce0d2c3ec889 100644 (file)
--- a/README
+++ b/README
@@ -1,34 +1,28 @@
-This directory contains the source code for the LTTng integration plugins for
-Eclipse, which includes the generic Tracing and Monitoring Framework (TMF).
+This source tree contains the source code for the Trace Compass plugins for
+Eclipse.
 
 The plugins are categorized as follows:
-org.eclipse.linuxtools.ctf.*          Common Trace Format (CTF) reader library
-org.eclipse.linuxtools.gdbtrace.*     Support for reading and viewing GDB traces
-org.eclipse.linuxtools.lttng2.*       LTTng 2.x integration
-org.eclipse.linuxtools.tmf.*          Tracing and Monitoring Framework
-org.eclipse.linuxtools.statesystem.*  State System library
-org.eclipse.linuxtools.tracing.rcp.*  Code specific to the RCP version
+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.tmf.*          Core framework
+org.eclipse.tracecompass.statesystem.*  State System library
+org.eclipse.tracecompass.rcp.*  Code specific to the RCP version
 
 See the plugins.svg file for a diagram showing the dependencies between the
 different plugins.
 
 
-To set up the environment to build TMF from within Eclipse, see this wiki page:
-http://wiki.eclipse.org/Linux_Tools_Project/LTTng_Eclipse_Plug-in_Development_Environment_Setup
+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, you first need to build the Linux Tools target definition
- (starting from the root of the source tree):
-$ cd releng/org.eclipse.linuxtools.target
+To build the plugins manually using Maven, simply run the following command from
+the top-level directory:
 $ mvn clean install
-Then you can build the LTTng plugins:
-$ cd ../../lttng
-$ mvn clean install
-
-As long as you don't clear the Maven reactor cache (in ~/.m2), you should not
-need to rebuild the target definition.
 
 
 The default command will compile and run the unit tests. Running the tests can
@@ -37,22 +31,23 @@ 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 "-PtracingRcp" to
+The RCP is not built by default, to build it you need to add "-Pbuild-rcp" to
 the 'mvn' command:
-$ mvn clean install -PtracingRcp -Dmaven.test.skip=true
+$ 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 lttng/org.eclipse.linuxtools.tracing.rcp.product/target/products
+will be placed in org.eclipse.tracecompass.rcp.product/target/products
 
 
-To build a local p2 update site (LTTng integration only)
-$ mvn clean install -PlttngPackage
+To build a local p2 update site
+$ mvn clean install -Pbuild-update-site
 
 This will place the p2 update site under the default location
-/var/www/tools/linuxtools/lttng/update-nightly/
+/var/www/tools/tracecompass/nightly/
 
 To change the package location, use:
-$ mvn clean install -PlttngPackage "-DlttngPackageDestination=<package destination>"
+$ mvn clean install -Pbuild-update-site "-DsiteDestination=<package destination>"
 
-where <package destination> is the absolute path to destination directory on your disk.
+where <package destination> is the absolute path to destination directory on
+your disk.