Type: New Feature
Resolution: Won't Do
Affects Version/s: None
Fix Version/s: None
Component/s: Plugins and Lifecycle
I think I miss configurable lifecycles... You can configure Maven plugin, but you can't configure maven lifecycle...
I think we should have some kind of packaging level configuration:
Plugins' executions should be configured (disabled/enabled) based on provided configuration.
You can already define custom lifecycles and lifecycle-mappings, but two or three custom lifecycles are not enough and you really need a family of similar, but slightly different lifecycles. Missing piece of puzzle is an ability to make them configurable. You can come close to this with properties and parent POMs, but it's not enough. Sometime properties should interact with each other and be something more than simple strings.
I know about profiles and I've used and abused them. But profiles don't solve the problem I'm talking about. What I want is to have single shared by organization, but slightly configurable lifecycle. You can customize almost everything in maven by explicit build configuration, but customizations are individual to each project and you can't by any means consolidate them...