Bugzilla – Full Text Bug Listing
| Summary: | [doc] Need doc describing how to run eclipse with Java WebStart | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Pascal Rapicault <pascal> |
| Component: | Runtime | Assignee: | Pascal Rapicault <pascal> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | ed.burnette, gmendel, gordon.hirsch, sgunturi |
| Version: | 3.1 | ||
| Target Milestone: | 3.1 RC3 | ||
| Hardware: | PC | ||
| OS: | Windows 2000 | ||
| Whiteboard: | |||
|
Description
Pascal Rapicault
set osgi.configuration.area to something like
@user.home/.myapplication
also suggest setting the
osgi.instance.area to the same value
eclipse.product must be specified
osgi.bundles is not required (inferred from the things listed in the JNLP files)
osgi.splashPath: use the JNLP mechanism
Indicate as well that - plugins must be jared - plugins must be signed - the application must run with full permissions Gordon Hirsch and I got this working with 3.1M5. Some extra steps were: - osgi plug-in jar needs to be flat (no jar in jar) - every plug-in has to have a manifest.mf (no auto-creation from plugin.xml) - in the eclipse.properties file in the root directory of the osgi plugin, you have to remove the framework classpath property (or maybe set it somewhere else, we didn't try that). - the other plug-ins accepted jars inside jars but I'm not sure if it's optimal. See http://www.eclipsepowered.org/archives/2005/02/23/deploying-with-jws/ for more info. It's good that you got it working because that was expected :-) See also bug #94141 The doc has just been released in HEAD. url? in the help system. it is in platform guide, under the deployement section. It is probably easy to search for Java Web Start or JNLP I've opened bug 100635 to request a live up to date help system on the web site so URLs for new help pages could be posted and they could be viewed in context as they would appear after an install of all the projects. |