On 4/2/11 3:48 AM, Anders Hammar wrote: >>> 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.
Yes, upon further reading this does appear to be correct. Plugins can create *new* lifecycles but the docs do not indicate an ability to change Maven's clean, default, and site lifecycles. >>> 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. Again, from the further information I've been able to dig up this appears to be true as well. It looks like the super POM has a plugin management section, setting the version of various plugins, but does not in fact attach any plugins to any phase of the standard lifecycles. Thanks to both Manfred and Anders for the discussion on this. -- Chad La Joie http://itumi.biz trusted identities, delivered --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
