On 4/6/07, Wim Deblauwe <[EMAIL PROTECTED]> wrote:
During testing of the webstart plugin that has the fix for
http://jira.codehaus.org/browse/MWEBSTART-13, I encountered the following
problem with the cooperation between the webstart and the site plugin.
Use case:
- There is 1 project that has a website generated by the site plugin. I want
to add a webstart link of that project in my generated site.
Problem:
The site plugin only deploys files that are in src/site. The
webstart-maven-plugin generates my jnlp file and my signed jars in
target/jnlp by default. If I want to reference that generated jnlp file from
within my generated website, I need to tell the webstart-maven-plugin to
generate in target/site/jnlp. That way in my apt files, I can create a link
to the jnlp file.
However, when doing a site:deploy, the directory target/site/jnlp is not
deployed. I would need a way to tell the site plugin to also copy that jnlp
directory.
Current workaround:
Generate the jnlp file and signed jars in src/site/resources/jnlp. That way,
the site plugin also deploys that directory. However, this mignles ofcourse
generated artifacts with sources, which I really don't want.
Any ideas on how to improve this?
have you tried to tell the webstart plugin to generate the files
inside target/site/jnlp by modifying the workDirectory variable ?
add something like
<configuration>
<workDirectory>${project.build.directory}/site/jnlp</workDirectory>
</configuration>
then try something like
mvn site webstart:jnlp
Jerome
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
