On Thu, Mar 15, 2012 at 8:04 AM, Amir Gheibi <[email protected]> wrote: > Hi Eric, > > I was wondering why your project POM's packaging type is "POM". If I > understand correctly, with "POM" packaging type you'd only get 3 default > goals bound to their phases (I read it here: > http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html#Built-in_Lifecycle_Bindings).
The top level pom's types are always pom. Since they never build any artifacts. The corporate one is more like a general defaults, so it doesn't build anything => use pom. The top level project often has modules, in which case it MUST be pom. Which other lifecycles did you expect to be able to run on something that doesn't itself build an artifact? This is not the same as being able to run "mvn compile" at the top level and have this command also run in all the modules. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
