On 11/6/06, Valerio Schiavoni [EMAIL PROTECTED] wrote:
dnameCn/dnameCn
dnameOu/dnameOu
dnameO/dnameO
dnameL/dnameL
dnameSt/dnameSt
dnameC/dnameC
i
répondre à
users@maven.apache.org
Pour
users
cc
Objet
Re: webstart-plugin: signing takes soo long..
On 11/6/06, Valerio Schiavoni [EMAIL PROTECTED] wrote:
dnameCn/dnameCn
dnameOu/dnameOu
dnameO/dnameO
hello everyone,
i'm trying to get my way wiith the java-webstart plugin. i'm quite a newbie
with it, sorry if i post silly questions.
i followed the tutorials here:
http://mojo.codehaus.org/webstart-maven-plugin-parent/webstart-maven-plugin/howto.html
first, i tried without signing the jars,
[...]
so, anyone has any idea on why it takes so long to sign them ? actually, i
don't even know if it ever finishes the whole process...
This may not be related to maven at all but I ran into slow signing when
I built my project on the server. On my workstation the signing of jars
was
hello dirk, thanks for your reply,
On 11/6/06, Dirk Olmes [EMAIL PROTECTED] wrote:
In the end it turned out to be the random device that is configured by
default in the jdk. Take a look at
$JAVA_HOME/jre/lib/security/java.security where the random device is
configured.
what should I check ?
Dirk is simply suggesting (I think) that you can/should check the
version and speed of your securerandom.source, and if signing jars
takes too long then you might need to look into a faster source.
There's not a lot the webstart plugin can do to improve the speed of
your random device.
If you
Valerio Schiavoni wrote:
hello dirk, thanks for your reply,
On 11/6/06, Dirk Olmes [EMAIL PROTECTED] wrote:
In the end it turned out to be the random device that is configured by
default in the jdk. Take a look at
$JAVA_HOME/jre/lib/security/java.security where the random device is
