| Re: [mdt-papyrus.dev] [SysML] Product Signing |
Hi, Moreover if you look at our HIPP job in charge of making the release we are activating the following profile for Papyrus components [2] eclipse-pack eclipse-sign product it is in the advanced view for maven job configuration [2]: https://hudson.eclipse.org/papyrus/view/Designer/job/papyrus-designer-neon/ De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] De la part de MAGGI Benoit Hi Celine, You may find your information here [1] Regards, Benoit De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] De la part de Céline JANSSENS Hello everyone, I’m working on signing the Papyrus RT product for the next release. But this is a first for me J In the Main pom there is a special profile with maven jarsigner for Packaging and Signing the product. [2] But it seems not signing as expected. In Papyrus, I see that a script.sh is responsible for signing, but I would like to avoid the use of script to do so. In SysML, in the job in charge of the SysML build [1], the profiles “eclipse-pack” and “eclipse-sign” are called. But I cannot find them in the pom of SysML. Does someone knows where are specified those profiles ? Do I need more than the eclipse-jarsigner-plugin and tycho-pack200b-plugin ? Best regards Céline 1: https://hudson.eclipse.org/papyrus/view/Sysml/job/papyrus-sysml-neon 2: http://maven.apache.org/plugins/maven-jarsigner-plugin/usage.html
|
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
