|
||||||||
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)
The site-lifecycle can trigger the build-lifecycle, for instance the cobertura-maven-plugin can do so. I don't want to modify the pom, especially not the build-section (about reporting-section we can discusss, but I'd prefer to leave it as it is). It should be possible to re-build the project and re-generate the site, since it has once been released. I'd prefer to restore the original environment and maybe the plugin can give hints.