Hi, I just released version 1.1.3-SNAPSHOT of CBI maven plugins. Please give it a try. You should only need to change the version from whatever you use to 1.1.3-SNAPSHOT. Here is the list of changes:
* A lot of things have changed under the hood to provide better reliability and the plugins are now extensively tested. * A new plugin has appeared (https://www.eclipse.org/cbi/sitedocs/1.1.3-SNAPSHOT/eclipse-dmg-packager/package-dmg-mojo.html <https://www.eclipse.org/cbi/sitedocs/1.1.3-SNAPSHOT/eclipse-dmg-packager/package-dmg-mojo.html>) thanks to Pascal Rapicault: the dmg packager. It gives you the possibility to package an OS X application as a DMG (Apple's .msi equivalent). Please note that this plugin is still in beta-stage, but feedback is more than welcome! * Two new options has been added to the jarsigner plugin (to fix https://bugs.eclipse.org/bugs/show_bug.cgi?id=473402 <https://bugs.eclipse.org/bugs/show_bug.cgi?id=473402>): - digestAlgorithm (https://www.eclipse.org/cbi/sitedocs/1.1.3-SNAPSHOT/eclipse-jarsigner-plugin/sign-mojo.html#digestAlgorithm <https://www.eclipse.org/cbi/sitedocs/1.1.3-SNAPSHOT/eclipse-jarsigner-plugin/sign-mojo.html#digestAlgorithm>) - resignStrategy (https://www.eclipse.org/cbi/sitedocs/1.1.3-SNAPSHOT/eclipse-jarsigner-plugin/sign-mojo.html#resigningStrategy <https://www.eclipse.org/cbi/sitedocs/1.1.3-SNAPSHOT/eclipse-jarsigner-plugin/sign-mojo.html#resigningStrategy>) * Non qualified properties (e.g. -DcontinueOnFail) have been deprecated in favor of qualified properties (-D cbi.jarsigner.continueOnFail) to avoid collision with other plugins. Non qualified properties are still supported, but they are implemented by parameter starting with "deprecated". It should not changed anything for people who don't use user properties (i.e. '-D' on the maven command line). If you do, you will see a deprecation warning. * Staging documentation is available here https://www.eclipse.org/cbi/sitedocs/1.1.3-SNAPSHOT/ <https://www.eclipse.org/cbi/sitedocs/1.1.3-SNAPSHOT/>. You will see that documentation for a low-level plugin is now available (https://www.eclipse.org/cbi/sitedocs/1.1.3-SNAPSHOT/eclipse-cbi-plugin/plugin-info.html <https://www.eclipse.org/cbi/sitedocs/1.1.3-SNAPSHOT/eclipse-cbi-plugin/plugin-info.html>) * A standalone test server is available to help people debug jar signing locally, without the need to run builds on the Eclipse servers. Just download https://repo.eclipse.org/content/repositories/cbi/org/eclipse/cbi/jar-signing-service/1.0.0-SNAPSHOT/jar-signing-service-1.0.0-20151020.095931-22.jar <https://repo.eclipse.org/content/repositories/cbi/org/eclipse/cbi/jar-signing-service/1.0.0-SNAPSHOT/jar-signing-service-1.0.0-20151020.095931-22.jar> and https://repo.eclipse.org/content/repositories/cbi/org/eclipse/cbi/jar-signing-service/1.0.0-SNAPSHOT/jar-signing-service-1.0.0-20151020.095931-22-tests.jar <https://repo.eclipse.org/content/repositories/cbi/org/eclipse/cbi/jar-signing-service/1.0.0-SNAPSHOT/jar-signing-service-1.0.0-20151020.095931-22-tests.jar> (or more recent) and run the following command java -cp /path/where/you/download/the/jars/jar-signing-service-1.0.0-20151020.095931-22.jar:/path/where/you/download/the/jars/jar-signing-service-1.0.0-20151020.095931-22-tests.jar: TestServer It will print an URL (like http://localhost:3138/jarsigner <http://localhost:3138/jarsigner>) that you can add to your maven build (-Dcbi.jarsigner.signerUrl=http://localhost:3138/jarsigner <http://localhost:3138/jarsigner>) and it will sign your jars locally with a dummy certificate. You can pass --help to see the options you can give to the TestServer Thanks. Mikael
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ cross-project-issues-dev mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
