[
http://jira.codehaus.org/browse/MWEBSTART-55?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jörg Henne updated MWEBSTART-55:
--------------------------------
Attachment: test case 2.zip
Thanks for looking into this! I've played (and debugged) around with the
jnlp-inline goal, but am still stuck.
First of all: the "senmantics" of my problem have shifted a bit: I no longer
try to go the "pom" route, but run the jnlp-inline goal within the project
creating my main JNLP application jar. If I modify my first test case to use
the jnlp-inline goal, everything works fine within this limited test case. So,
the stuff below could be seen as a separate problem. I'll keep the description
here, anyway.
"Test case 2.zip" contains a simple two subproject multi-module setup. test:a
creates a jar, and creates a webstart zip containing some other stuff (web.xml,
jnlp-servlet.jar) to make up a complete download war. This war is then renamed
into a war and attached to the build. Project b subsequently references the
created war (this would, in reality, be a project to build an ear).
The trouble, is, however, that if the execution of the webstart-maven-plugin is
present, the two other plugin executions don't occur. Maven seems to try to
immediately build project b after creating the project a jar. If the execution
of webstart-maven-plugin is removed from project a, and a fake output
(a-1.0-SNAPSHOT.zip) is dropped into "target", to simulate a successful
execution, everything works fine. I didn't quite find out what causes this
behaviour, and I don't think that any of the examples in plugin/test/projects
cover this situation.
> Mojo fails when packaging is pom
> --------------------------------
>
> Key: MWEBSTART-55
> URL: http://jira.codehaus.org/browse/MWEBSTART-55
> Project: Maven 2.x Webstart Plugin
> Issue Type: Bug
> Affects Versions: 1.0-alpha-2
> Reporter: Jörg Henne
> Attachments: test case 2.zip, test case.zip
>
>
> The documentation says that the maven-webstart-plugin is applicable to jar
> and pom packaging types. However, if pom is used, the build fails, since the
> dependencies end up being empty, no matter what dependencies are specified.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
