>> > Each lifecycle is made up of a fixed, ordered list, of phases. The >> > phases in each lifecycle are also defined by Maven core and can not be >> > changed by plugins. >> >> Not correct. They can be changed. E.g the maven android plugin changes >> it.. >> > > I'm quite sure he is correct. The ordered list of phases for the three > lifecycles in Maven core cannot be changed.
I am pretty sure they can be changed. I kind of remember references to that. But I might be wrong. However a plugin can definitely change what happens in each lifecycle phase. >>> > Goals, defined in various plugins, are attached to specific phases in >> > order to create the actual "executable" lifecycle. >> >> Yes.. this is defined in the super pom. >> > > No, it's not defined in the super POM. Some bindings are defined by the > packaging type that you declare in your project. Others you add yourself > in > your pom under build/plugins. Correct. Sorry for the mix up. Some executions are defined on the super pom but only for performing a release. But the super pom defines a lot of plugin versions and therefore indirectly packaging types.. and then we are back to your point ;-) manfred --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
