Ah, I see. That's another cause then - thanks for pointing it out. That's already scheduled to be reported in 2.0.1.
On 11/18/05, Mordo, Aviran (EXP N-NANNATEK) <[EMAIL PROTECTED]> wrote: > I am so stupid :-| I had the same artifactId in both the parent and the > module > > It is resolved now. Thank you > > -----Original Message----- > From: Brett Porter [mailto:[EMAIL PROTECTED] > Sent: Thursday, November 17, 2005 3:09 PM > To: Maven Users List > Subject: Re: No goals needed for project - skipping > > On 11/18/05, Mordo, Aviran (EXP N-NANNATEK) <[EMAIL PROTECTED]> > wrote: > > I'm trying to build a multi project application. I have a pom.xml file > > > which has a default goal of package, and is building several sub > > modules. > > > > On one of the modules I always get a message "No goals needed for > > project - skipping" Why is that? How can I make it compile and test. > > > > BTW: If I run the reluctant project directly (not thru the parent pom > > it works good), just when I try to run it thru the parent it does not > > do anything but displaying the message "No goals needed for project - > > skipping" > > Are you sure it says that for your project, or does it say that for the > parent? It means that module has a packaging of POM or something else > that doesn't define any goals for the lifecycle step you are running. > > - Brett > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
