|RE: [buckminster-dev] create.eclipse.jnlp.product issues|
I succeeded in making a jnlp thing with both buckminster, and headless buckminster. The solution for (A) was unsigning all jars, the correct way to do so is with this ant-extension: http://code.google.com/p/existdb-contrib/wiki/ASOCAT Then another problem arised: the generated org.eclipse.equinox.executable_3.3.200.v20090521-1800-7M-Fm-FI3UouOe61h3BYGC.jnlp has no jnlp/information/vendor node, and the jnlp-client therefore refuses to proceed. I simply had to add that node to get it working. So here's my userguide to make a webstartable with buckminster: make a releng-feature that includes all my code own, plus the eclipse.rcp, eclipse.platform, eclipse.equinox.executable and run create.eclipse.jnlp.product there. in each *.jnlp remove the features/ prefix in the extension nodes. remove reference to plugin/...wpf... jars in rcp.jnlp and equinox.executable jnlp's remove reference to plugin/...compare.win32 in platform jnlp add WEB-INF/web.xml and WEB-INF/lib/jnlp-servlet.jar in the war add jnlp/information/vendor node in equinox.executable jnlp unsign all plugin/*.jar via ant and http://code.google.com/p/existdb-contrib/wiki/ASOCAT sign all plugin/*.jar with own certificate add a boot.jnlp (http://help.eclipse.org/stable/index.jsp?topic=/org.eclipse.platform.doc.isv/guide/java_web_start.htm) in the war and make sure it refers to the correct launcher jar (version) and to the correct jnlp DISCLAIMER: Unless indicated otherwise, the information contained in this message is privileged and confidential, and is intended only for the use of the addressee(s) named above and others who have been specifically authorized to receive it. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this message and/or attachments is strictly prohibited. The company accepts no liability for any damage caused by any virus transmitted by this email. Furthermore, the company does not warrant a proper and complete transmission of this information, nor does it accept liability for any delays. If you have received this message in error, please contact the sender and delete the message. Thank you.