Details
-
Bug
-
Status: Resolved (View Workflow)
-
Blocker
-
Resolution: Not A Defect
-
None
Description
javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: vfs:/content/jenkins.war/WEB-INF/lib/jenkins-core-1.525.jar/hudson/model/AbstractBuild/index.jelly:67:61: <st:include> No page found 'digest.jelly' for class hudson.maven.MavenModuleSetBuild
at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:117)
at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:673)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:777)
at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:381)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:684)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:777)
Attachments
Issue Links
- is related to
-
JENKINS-23150 Warn users about invalid plugin configurations
-
- Resolved
-
This actually is already the case, based on hudson.ClassicPluginStrategy#DETACHED_LIST
BUT such (implicit) plugin dependecy is set as optional, and user can disable them without a warning. This breaks git-plugin when mailer plugin is disabled, but no way to fix afaik until git-plugin uses recent jenkins as base - something I want to avoid as MANY users are still running pretty old jenkins instances (even < 1.480).
Would make sense anyway to make mailer dependency conditional in git-plugin, checking for hudson.task.Mailer class to be available in classpath.