Same thing for me. I didn't notice it. I prefer the older behavior.

cheers

arnaud

On Thu, Apr 17, 2008 at 3:41 PM, Brian E. Fox <[EMAIL PROTECTED]> wrote:
> I also think the new defaults aren't really helpful. IMO it should support 
> two modes: prompting the way it does in alpha-1/2 and by passing the info in 
> the form of properties.
>
>
>
>  -----Original Message-----
>  From: Brett Porter [mailto:[EMAIL PROTECTED]
>  Sent: Thursday, April 17, 2008 5:27 AM
>  To: Maven Developers List
>  Subject: Re: prompt behaviour changes was: [VOTE] Release Maven Archetype 
> plugin version 2.0-alpha-3
>
>
>  On 16/04/2008, at 1:19 AM, Raphaël Piéroni wrote:
>
>  >>> I found a regression in :generate -
>  >>> 1) the default (15) is no longer present
>  >>
>  >> This is not intended.
>  >
>  > This is a side effect of the new version of the internal catalog.
>  >
>  > Brett, may you please create a issue for it, i think we can live
>  > with that known bug and schedule it for alpha-4.
>  >
>  > If any one see it as a show stopper, i will fix it.
>
>  Done.
>
>  >>> 2) it no longer prompts for the groupId/etc - it goes straight to
>  >>> using
>  >>> some default settings
>  >>
>  >> This is partially intended.
>  >> the plugin now provides default for all values and
>  >> should ask for confirmation if everithing is correctly set.
>  >
>  > What the archetype plugin do is this:
>  > a. it ask for the archetype to use (il the list)
>  > b. It then guess sensible default values for common properties and
>  > additional properties.
>  > c. It then ask for any unguessed value.
>  > d. It then ask for confirmation about what was guessed/asked
>  > Yes this means that it only ask for confirmation when it guess all
>  > (common properties are always guessed)
>  > e. If it is not confirmed, it ask for each property a new values
>  > (proposing to keep the guessed value)
>  >
>  > I think this could is a better behaviour than before and permit to
>  > an user creating an archetype to provide some default values even for
>  > the common properties (like a default groupId in a corporate
>  > environment)
>
>  I think I prefer the previous behaviour, since most of the default
>  values are not intended to be kept (eg, com.example as a groupId). I
>  like just seeing the default, pressing enter, and continuing that way
>  than having to answer "N" every time and then do the same anyway. Just
>  IMHO :)
>
>  - Brett
>
>  --
>  Brett Porter
>  [EMAIL PROTECTED]
>  http://blogs.exist.com/bporter/
>
>
>  ---------------------------------------------------------------------
>  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]
>
>



-- 
..........................................................
Arnaud HERITIER
..........................................................
OCTO Technology - aheritier AT octo DOT com
www.octo.com | blog.octo.com
..........................................................
ASF - aheritier AT apache DOT org
www.apache.org | maven.apache.org
...........................................................

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to