[
http://jira.codehaus.org/browse/MWEBSTART-62?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_120801
]
Jerome Lacoste commented on MWEBSTART-62:
-----------------------------------------
A lot of good comments from Erik:
{code}
Some initial comments*:
* I'm still think the difference between jnlp and jnlp-inline should be
stated more clearly.
* In how many ways can the webstart-maven-plugin be used?
Is it correct that webstart files can be generated either _staticly_
(build-time) or _dynamicly_ with or without jnlp download servlet?
(Making it three different approaches?)
And that for each of these we have the following dimensions;
- single-module or multi-module
- war or jar
?
In my experience, it is hard to grasp the differences between these
different combinations. Users need overly simplistic docs I think.
See the attachment for how I have documented webstart usage for internal
use. (This covers single- and multi-module configuration for jar projects.)
*Suggestions*:
1. Create one page that explains the different approaches war/jar,
single-/multi-module and static/dynamic/dynamic w/jnlp download servlet.
+ links to the same sites as linked to under 3 (2a, 2b, 2c). The goal is
to explain when each approach is appropriate.
2. Create one page that explains the different types on use of
certificates; generate a new certificate on every build and use a
keystore. + how to generate a self-signed certifcate.
Both pages should link directly to complete, working examples or even
better, have the configuration listed.
3. Make the list under "Getting started" at
http://coffeebreaks.org/tmp/maven-staging/webstart/site/index.html the
"cookbook recipe" for how to use the plugin.
E.g:
1. read the Jnlp Mojos overview
2. decide your deployment strategy:
2a with static pages (link to a separate page with thorough
descriptions and an example)
2b within a WAR (link to a separate page with thorough descriptions
and an example)
2c within a WAR that uses Sun's Download Servlet (link to a separate
page with thorough descriptions and an example)
3. test your build (e.g. adding the Jetty server to your project)
The pages under 2a, 2b, 2c should be the main sources for using the
plugin. The resource pages under 1 and 2 are additional resources for
learning more about deployment strategies and certificates and should
not contain information strictly necessary for configuring the plugin.
4. The jar -signing process is really verbose. Perhaps the output could
be something like:
"Signing jar files:
jar-file1
jar-file2
jar-file3
All dependencies signed successfully. "
Instead of
[debug] jarsigner
executable=[/usr/lib/jvm/java-1.5.0-sun-1.5.0.13/jre/../bin/jarsigner]
[debug] Executing: /bin/sh -c "cd
/home/erik/dev/projectName/trunk/target/jnlp &&
/usr/lib/jvm/java-1.5.0-sun-1.5.0.13/jre/../bin/jarsigner -verify
/home/erik/dev/projectName/trunk/target/jnlp/lib/servlet-api-2.3.jar"
[info] jar verified.
{code}
> Improve documentation before next release
> -----------------------------------------
>
> Key: MWEBSTART-62
> URL: http://jira.codehaus.org/browse/MWEBSTART-62
> Project: Maven 2.x Webstart Plugin
> Issue Type: Task
> Components: doc
> Reporter: Jerome Lacoste
> Fix For: 1.0-alpha-3
>
> Attachments: MWEBSTART-62-1.txt, webstartDemo.zip
>
>
> Some of the things that could be improved. Not everything will be detailed.
> * Description of jnlp, jnlp-inline and jnlp-single goals. What is the
> difference?
> * Easier to find examples of template.vm and configuration of the
> webstart-plugin. (I can send you a couple of working configurations if
> you're interested.)
> * Use separate module for webstart-plugin definition in multimodule
> maven projects.
> * Examples on use of generated keystore and using a single keystore.
> * A description of _when_ to use the jnlpDownloadServlet. Descriptions
> of common use cases are always very useful.
> * Links to additional resources on certificates, jar signing, Java
> webstart, keytool,
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
