Now there is no error message, but at "http://hudson-installation/job/the-project/build-number" there is still a list of disabled/removed modules

I've tried the Groovy script on the wiki, but even if it completes successfully I still have the disabled modules listed...

Jenkins version is 1.635, latest available for what I know.

After a little investigation running the following script highlighted the modules are not marked as disabled: no wonder they are not deleted!

import hudson.model.*
import hudson.maven.*

hudson.model.Hudson.instance.items.findAll{job -> job instanceof MavenModuleSet}.each {
job ->
  job.getModules().each { module -> println(module.name + " found " + module.disabled) }
  job.getDisabledModules(true).each {
    module -> module.delete()
    println(module.name + " deleted")
  } 
  println(job.name + " cleaned")
}

Since it seems like modules aren't correctly being marked disabled, I have been manually removing them after refactoring with this code:
(updating the module name by hand based on what no longer exists/didn't run)

import hudson.model.*
import hudson.maven.*

hudson.model.Hudson.instance.items.findAll{job -> job instanceof MavenModuleSet}.each {

  job ->
  println("Job: " + job.name)  
  job.getModules().each {
    module ->
    print("  " + module.name + " (disabled = " + module.disabled + ")")
    if ("someModuleYouNoLongerWant".equals(module.name)) {
      module.delete() 
      println(" <-- deleted module " + module.name)
    } else {
      println("");
    }    
  }  
}

Hi guys,
is there any news about this?
Thanks
Cheers
Davide

This also affects Jenkins 2.23, see http://stackoverflow.com/questions/39791774/how-to-remove-outdated-maven-artifacts-from-jenkins-maven2-3-job

There is a little glitch with the script workaround: Archived builds will loose their modules of the build relevant to that build time. Sadly, this seems to be unrecoverable after applying the workaround. Might be tragic for others, for me it is OK atm.