I find it super convenient: 1. For multi modules project since I dont have keep enter a goal on command line. Verify goal is not good enough since I need all artifacts in be installed on local repository 2. I can jump between modules to build individually
What is your reason for 'verify' goal? -D On Mon, Nov 11, 2013 at 9:46 AM, Robert Scholte <codeh...@sourcegrounds.com>wrote: > Hmm, I'm not a huge fan of the defaultGoal and especially not if it is > install. > I'd prefer 'verify' instead. > > Robert > > Op Mon, 11 Nov 2013 00:34:40 +0100 schreef <dant...@codehaus.org>: > > Revision: >> >> 18914 >> Author: >> >> dantran >> Date: >> >> 2013-11-10 17:34:39 -0600 (Sun, 10 Nov 2013) >> >> Log Message >> >> Add defaultGoal at top level pom >> >> Modified Paths >> >> trunk/mojo/appassembler/pom.xml >> >> Diff >> >> Modified: trunk/mojo/appassembler/pom.xml (18913 => 18914) >> >> >> >> --- trunk/mojo/appassembler/pom.xml 2013-11-10 07:36:22 UTC >> (rev 18913) >> +++ trunk/mojo/appassembler/pom.xml 2013-11-10 23:34:39 UTC >> (rev 18914) >> >> @@ -183,6 +183,9 @@ >> >> >> >> <build> >> >> + >> + <defaultGoal>install</defaultGoal> >> + >> >> <pluginManagement> >> >> <plugins> >> >> <plugin> >> >> To unsubscribe from this list please visit: >> >> http://xircles.codehaus.org/manage_email >> > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > >
