[
http://jira.codehaus.org/browse/MWEBSTART-32?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95645
]
Stephane Nicoll commented on MWEBSTART-32:
------------------------------------------
use dependency:resolve to see what's going on.
Not sure I understand your problem though. If this is a plugin plugin issue,
just add a plugin section for the maven-plugin-plugin with version 2.3
> Class 'org.codehaus.mojo.webstart.SignConfig' cannot be instantiated
> --------------------------------------------------------------------
>
> Key: MWEBSTART-32
> URL: http://jira.codehaus.org/browse/MWEBSTART-32
> Project: Maven 2.x Webstart Plugin
> Issue Type: Bug
> Affects Versions: 1.0-alpha-2
> Environment: Maven 2.0.5, Maven 2.0.6
> Reporter: Ken Geis
> Assignee: Jerome Lacoste
> Fix For: 1.0-alpha-2
>
>
> With the April 3 snapshot, I get the following error message:
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Failed to configure plugin parameters for:
> org.codehaus.mojo:webstart-mav
> en-plugin:1.0-alpha-2-SNAPSHOT
> Cause: Class 'org.codehaus.mojo.webstart.SignConfig' cannot be instantiated
> [INFO]
> ------------------------------------------------------------------------
> I'm guessing that this is because the POM declares webstart-jarsigner-api as
> a compile-time dependency, and it is probably also needed at runtime.
--
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
