JavawebstartForRCPEval

Enhancements for Java Web Start (JWS) support for RCP applications

fix dichotomy between building JNLP descriptors for platform using the harness (which is very fragile) vs. using prebuilt JNLP descriptors from ${jnlp.platform.codebase} (which makes it hard to reuse a specific platform and does not support "suite chaining"), perhaps by including JNLP descriptors as a mandatory part of platforms and NBMs

better documentation for JWS support for NB RCP apps; currently documentation consists of chaotic mixture of READMEs, bug reports, builds scripts, property files, error messages, blogs, tutorials

more options for customization via UI:
- initial heap size, max heap size
- required Java version
- JVM args

option for compression of app using Pack200. Support for pack200 will be added for J2SE project too, so some coordination would be useful at least not to duplicate effort and to have the same or similar UI.

provide JnlpServlet impl specific for NBM files and their versioning scheme (extension elements of master.jnlp do not use version attribute for each component); align JNLP provisioning with Plugin Manager semantics

support for bundling native libraries along with app in JNLP mode; extbrowser/build.xml shows it is possible, but not straightforward

deployment of final application WAR to supported Java EE application server (currently can only build WAR from apisupport). We will need some support from Web team in this matter, either to provide API for deployment or at least custom Ant task for deployment.

UI for certificate and signature handling (already in Java ME, should be reused; should probably be part of ide cluster)

we should publish every release and major build of NB RCP (milestones, betas, RCs) and some recent dev builds to allow users to use it for their applications (release builds) and for testing (dev builds and major builds). Should be published on one well known and maintained location. Seems to be already working to some extent but should be consolidated and publicized. Known location should be shown in IDE UI in list. - This brings the problem that user might be developing locally against different versions than our published jnlp codebase. It can be solved either by warning to user (minimal solution) or by downloading correct sources coresponding with selected codebase (maximal solution).

make configuration less complex, have UI for showing all JWS related settings (mainly properties) on one place

have clear distinction (and documentation) of what is set automatically (e.g. by selecting specific platform), what needs to be set by developer by hand (and where)

RE - Consolidation of published JNLP descriptors for NB major releases
Web - API or other support (Ant task) for deployment of final application war file
Java - pack200 support for J2SE projects coordination