Hi Jerome:
I think I might have a workaround... I have a separate client.jnlp
project that uses the jnlp plugin and I will move those target artifacts
to my war.
That being said, I'm getting an exception at the template.vm.
The exception is:
Caused by: java.lang.IllegalArgumentException: Could not load the
template file from
'C:\workspace\manager\client.jnlp/src/jnlp/template.vm'
Here's my template.vm:
<?xml version="1.0" encoding="utf-8"?>
<jnlp spec="1.5+" codebase="$$codebase" href="client.jnlp">
<information>
<title>Client</title>
<vendor>Example</vendor>
<shortcut>
<desktop/>
</shortcut>
</information>
<security>
<all-permissions/>
</security>
<resources>
<j2se version="1.5+"
initial-heap-size="64m"
max-heap-size="128m"
href="http://java.sun.com/products/autodl/j2se"/>
$dependencies
</resources>
<application-desc main-class="$mainClass"/>
</jnlp>
Any help is appreciated,
Christiaan
-----Original Message-----
From: jerome lacoste [mailto:[EMAIL PROTECTED]
Sent: Monday, May 08, 2006 1:49 PM
To: [email protected]
Subject: Re: [mojo-user] maven-webstart-plugin: dependencies include
On 5/8/06, Veerman, Christiaan <[EMAIL PROTECTED]> wrote:
> Hi Jerome:
>
> The webstart plugin will not transitively add the dependencies if I
> assign the scope of provided.
>
> Basically, I want to sign jars in the root of the war and not
> duplicate the jars to WEB-INF/lib.
>
> If anyone can help it would be greatly appreciated.
Can't you:
- keep your deps in compile scope in your webstart project
- redefine the dependencies in your war and override the scope to
provided
?
It breaks the DRY principle but I don't see another way to do it today.
I am not sure how to accomodate your use case within the plugin itself.
Jerome
****DISCLAIMER
The information contained in this e-mail and attachments, if any, is
confidential and may be subject to legal privilege. If you are not the
intended recipient, you must not use, copy, distribute or disclose the e-mail
and its attachment, or any part of its content or take any action in reliance
of it. If you have received this e-mail in error, please e-mail the message
back to the sender by replying and then deleting it. We cannot accept
responsibility for loss or damage arising from the use of this e-mail or
attachments, and recommend that you subject these to your virus checking
procedures prior to use
