I have seen this on some Maven module builds, especially ones where only some of the modules in the pom are build, e.g. by using `-pl some-module -am`
The MavenModuleSet will have both lastSuccessfulBuild and lastStableBuild defined.
The individual MavenModule instances, however, will only have lastStable defined.
Originally reported by
stephenconnolly, imported from: New lazy loading permalinks can break job.lastStableBuild != null => job.lastSuccessfulBuild != null
- assignee:
jglick
- status: Resolved
- priority: Major
- component(s): core, maven-plugin
- label(s): 1.509.4-fixed, lazy-loading, permalink, symlink
- resolution: Fixed
- resolved: 2013-08-20T18:21:25+00:00
- votes: 0
- watchers: 3
- imported: 2025-11-24
Raw content of original issue
I have seen this on some Maven module builds, especially ones where only some of the modules in the pom are build, e.g. by using `-pl some-module -am`
The MavenModuleSet will have both lastSuccessfulBuild and lastStableBuild defined.
The individual MavenModule instances, however, will only have lastStable defined.
I have seen this on some Maven module builds, especially ones where only some of the modules in the pom are build, e.g. by using `-pl some-module -am`
The MavenModuleSet will have both lastSuccessfulBuild and lastStableBuild defined.
The individual MavenModule instances, however, will only have lastStable defined.
Originally reported by
stephenconnolly, imported from: New lazy loading permalinks can break job.lastStableBuild != null => job.lastSuccessfulBuild != null
Raw content of original issue