[mojo-user] WebStart Maven Plugin Issue

[Michael Feshin]

Hi,

I'm trying to use Webstart Maven Plugin to build a JNLP application within
a WAR package which uses JnlpDownloadServlet. It appears so that some of
signed progect dependencies got incorrect names. For example
"json-lib-2.3-jdk15.jar" library has been renamed to
"json-lib-jdk15-2.3.jar". At the same time generated version.xml file maps
this library to the original "json-lib-2.3-jdk15.jar" name. This causes
"Unable to load resource" exception when application is launched.

The plugin configuration:
            <plugin>
                <groupId>org.codehaus.mojo</groupId>
                <artifactId>webstart-maven-plugin</artifactId>
                <version>1.0-beta-6</version>
                <executions>
                    <execution>
                        <phase>process-resources</phase>
                        <goals>
                            <goal>jnlp-download-servlet</goal>
                        </goals>
                    </execution>
                </executions>

                <configuration>
                    <verbose>true</verbose>
                    <outputJarVersions>false</outputJarVersions>

<outputDirectoryName>${webstart.app.path}</outputDirectoryName>
                    <libPath>lib</libPath>
                      <excludeTransitive>false</excludeTransitive>
                    <jnlpFiles>
                        <jnlpFile>
                            <inputTemplate>template.vm</inputTemplate>
                            <outputFilename>${webstart.app.name
}.jnlp</outputFilename>
                            <jarResources>
                                <jarResource>
                                    <groupId>${webstart.app.group.id
}</groupId>
                                    <artifactId>${webstart.app.artifact.id
}</artifactId>

<version>${webstart.app.version}</version>

<mainClass>${webstart.app.mainclass}</mainClass>
                                </jarResource>
                            </jarResources>
                        </jnlpFile>
                    </jnlpFiles>
                    <!--Automatically signs the jar and its dependencies-->
                    <sign>
                      -------------------
                    </sign>
                    <!--Unsign already signed packages and sign them with
own key-->
                    <unsign>true</unsign>
                    <!--<verifyjar>false</verifyjar>-->
                </configuration>
            </plugin>

The same problem takes place in case of time stamped artifact snapshots.

Is it some known bug or I have missed something in the plugin configuration?

Kind regards,
Michael