|
||||||||
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
- [mojo-dev] [jira] (MOJO-1826) NoClassDefFoundError... Anders Hammar (JIRA)
- [mojo-dev] [jira] (MOJO-1826) NoClassDefFound... Robert Scholte (JIRA)
- [mojo-dev] [jira] (MOJO-1826) NoClassDefFound... Anders Hammar (JIRA)
- [mojo-dev] [jira] (MOJO-1826) NoClassDefFound... Anders Hammar (JIRA)
- [mojo-dev] [jira] (MOJO-1826) NoClassDefFound... Robert Scholte (JIRA)
- [mojo-dev] [jira] (MOJO-1826) NoClassDefFound... Dennis Lundberg (JIRA)
- [mojo-dev] [jira] (MOJO-1826) NoClassDefFound... Anders Hammar (JIRA)
- [mojo-dev] [jira] (MOJO-1826) NoClassDefFound... Robert Scholte (JIRA)
- [mojo-dev] [jira] (MSITESKIN-3) NoClassDefFou... Stephen Connolly (JIRA)
So the latest version of jboss-packaging-maven-plugin contains plugins which are not compatible with Maven3. In that case you must use Maven2 to run the siteskinner-maven-plugin.
What is your wish? Apparently Maven3 considers this as a warning, not an error, otherwise the plugin would fail too.
I'm not sure what I can do here...