[mojo-user] "JAR resources in jnlp file are not signed by the same certificate (was: "Re: java webstart plugin: sign (one/all) depnendencies?)

[Jan Torben Heuer]

Jerome Lacoste wrote:

>> How can I tell the plugin to also sign all dependencies - or at minimum
>> one of them? They want to access the filesystem so (AFAIK) they have to
>> be signed, too.
> 
> The plugin should sign all your dependencies. If it doesn't:
> 
> * try to use the jnlp-inline mojo instead
> * try to use -X to see the debugging information

Thanks, the inline mojo seems to help a bit, now I get the error message:

"JAR resources in jnlp file are not signed by the same certificate"

What happened? I did a:

mvn clean install
org.codehaus.mojo.webstart:webstart-maven-plugin:jnlp-inline

and later:
javaws -verbose -offline -codebase $fullpath diki.jnlp

The pom file is configured with:
<plugin>
        <groupId>org.codehaus.mojo.webstart</groupId>
        <artifactId>webstart-maven-plugin</artifactId>
        <executions>
                <execution>
                        <goals>
                                <goal>jnlp</goal>
                        </goals>
                </execution>
        </executions>
        <configuration>
                <excludeTransitive>false</excludeTransitive>
                <libPath>lib</libPath>
                <jnlp>
                        <outputFile>diki.jnlp</outputFile><!-- defaults to 
launch.jnlp -->
                        <!-- this is perhaps going to change -->
                        <mainClass>foo.diki.gui.Main</mainClass>
                </jnlp>

                <sign>
                        <keystore>${basedir}/src/main/keys/diki.key</keystore>
                        <keypass>nopass</keypass>
                        <storepass>nopass</storepass>
                        <!--storetype>fillme</storetype-->
                        <alias>diki.alias</alias>
                        <!--validity>fillme</validity-->
                        <!-- only required for generating the keystore -->
                        <dnameCn>Jan</dnameCn>
                                <dnameOu>xyz</dnameOu>
                                <dnameO>foo</dnameO>
                                <dnameL>NRW</dnameL>
                                <dnameSt>NRW</dnameSt>
                                <dnameC>Germany</dnameC>

                        <verify>true</verify><!-- verify that the signing 
operation succeeded -->

                        <!-- KEYSTORE MANAGEMENT -->
                        <keystoreConfig>
                                <delete>true</delete><!-- delete the keystore 
-->
                                <gen>true</gen><!-- optional shortcut to 
generate the store. -->
                        </keystoreConfig>
                </sign>
                <pack200>true</pack200>
                <gzip>true</gzip>
                <outputJarVersions>true</outputJarVersions>

                <verbose>true</verbose>

        </configuration>
</plugin>

Any ideas what could have happened?


Jan



---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email