The "update site" (in releng-site/target/repository) is always
built, so this is more akin to the "deploy-rcp" profile that
is used for the RCP.
Change-Id: Ide082f2738a61e326b5e35eb41b0e6aa38198fc4
Signed-off-by: Alexandre Montplaisir <alexmonthy@voxpopuli.im>
Reviewed-on: https://git.eclipse.org/r/40512
Reviewed-by: Marc-Andre Laperle <marc-andre.laperle@ericsson.com>
Tested-by: Marc-Andre Laperle <marc-andre.laperle@ericsson.com>
Reviewed-by: Hudson CI
To build a local p2 update site:
- mvn clean install -Pbuild-update-site "-DsiteDestination=/path/to/destination"
+ mvn clean install -Pdeploy-update-site "-DsiteDestination=/path/to/destination"
where `/path/to/destination` is the **absolute** path to destination directory
on your disk.
<profiles>
<profile>
- <id>build-update-site</id>
+ <id>deploy-update-site</id>
<properties>
<siteDestination>/home/data/httpd/download.eclipse.org/tracecompass/master/nightly/</siteDestination>
</properties>