Skip to main content
diff options
authorMarkus Knauer2014-11-12 17:39:22 +0000
committerMarkus Knauer2014-11-12 17:39:22 +0000
commit2ebce8f0d340d4229d988bea421a0e3909876aed (patch)
tree97700e74b72ba89499f0b1c7aafca85f8ee6e1c8 /
parentb573981368660b6a5392a27c4efb18bae37f5160 (diff)
Allow fine grained control over used signing services
EPP uses all three currently available signing services from at the Eclipse Foundation. The general signing service to sign the jar files, the Windows signing service for the Windows executable, and the Mac OSX signing service for various Mac-related signatures. With this change it is possible to control by enabling Maven profiles which signing services are used during build time. Bug 451139: Unable to sign Mac OSX packages from EPP HIPP instance Change-Id: If2ccd76d85aec2136520e4cbdd397115fa36fb01 Signed-off-by: Markus Knauer <>
Diffstat (limited to '')
1 files changed, 4 insertions, 2 deletions
diff --git a/ b/
index cc493d86..10e62e13 100644
--- a/
+++ b/
@@ -58,11 +58,13 @@ Each package uses its own profile:
- epp.package.scout
- epp.package.testing
-With the signing profile enabled, the build artifacts (bundles, features) and the
+With the signing profiles enabled, the build artifacts (bundles, features) and the
Windows and Mac OSX executables are signed. This is done by using the Eclipse Foundation
internal signing service and can be activated only if the build is running there.
-- eclipse-sign
+- eclipse-sign-jar profile enables signing of the EPP bundles and jar files
+- eclipse-sign-mac profile enables usage of Mac OSX signing service
+- eclipse-sign-windows profile enables usage of Windows signing service
Additional Configuration Possibilities

Back to the top