Community
Participate
Working Groups
Build currently supports signing (and to some degree pack200 conditioning) during the build. This is necessary for JNLP builds. When publishing from source, we are publishing directly into a p2 repository. We either need to sign and condition during the publish, or have a publisher action that goes over a repo and signs/conditions it. Build currently extends the JarProcessor to support using ant for signing, as well as unsigning, and conditioning.
I've started this, code is currently in org.eclipse.equinox.p2.repository.tools it is a task that conditions a repo (sign/pack) and updates the artifacts.xml
Done. The ant task eclipse.jarProcessor is moved from pde.build to org.eclipse.equinox.p2.jarprocessor. It supports signing using the ant sign task. There is a new task p2.process.artifacts provided by org.eclipse.equinox.p2.repository.tools This task has the form <p2.process.artifacts repositoryPath="file:/path/repo" pack="true" (optional) normalize="true" (optional) <sign keystore="/path/keystore" keypass="keypass" storepass="storepass" alias="alias" unsign="true" /> </p2.process.artifacts> The p2.process.artifacts task delegates to the eclipse.jarProcessor task for signing and packing. The task will do the right thing wrt to conditioning and signing. The unsign attribute indicates that any existing signatures should be removed from the jar. I raised bug 265726 to change pde.build to use this task to sign when publishing from source.