You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Brett Porter <br...@apache.org> on 2008/04/17 11:26:44 UTC
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
brett@apache.org
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: prompt behaviour changes was: [VOTE] Release Maven Archetype plugin version 2.0-alpha-3
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
Don't hard code anything, then if there is already a value, use that otherwise prompt.
-----Original Message-----
From: Raphaël Piéroni [mailto:raphaelpieroni@gmail.com]
Sent: Thursday, April 17, 2008 2:38 PM
To: Maven Developers List
Subject: Re: prompt behaviour changes was: [VOTE] Release Maven Archetype plugin version 2.0-alpha-3
So to sum up on the behaviour,
What is desired is :
- ask for each property (proposing a default value when guessed)
- then ask for confirmation.
Currently the configuration behaviour do not know from where
comes the default values. They can come from :
- some hard coded (groupId=com.company, artifactId=quickstart,
version=1.0-SNAPSHOT, package=$groupId)
- the archetype-metadata.xml file,
- the command line options
If we go on the way defined above,
then every property will be asked.
Raphaël
2008/4/17, Arnaud HERITIER <ah...@gmail.com>:
> Same thing for me. I didn't notice it. I prefer the older behaviour.
>
> cheers
>
> arnaud
>
>
> On Thu, Apr 17, 2008 at 3:41 PM, Brian E. Fox <br...@reply.infinity.nu> 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:brett@apache.org]
> > 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
> > brett@apache.org
> > http://blogs.exist.com/bporter/
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
> >
>
>
>
>
> --
> ..........................................................
>
> 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: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: prompt behaviour changes was: [VOTE] Release Maven Archetype plugin version 2.0-alpha-3
Posted by Raphaël Piéroni <ra...@gmail.com>.
So to sum up on the behaviour,
What is desired is :
- ask for each property (proposing a default value when guessed)
- then ask for confirmation.
Currently the configuration behaviour do not know from where
comes the default values. They can come from :
- some hard coded (groupId=com.company, artifactId=quickstart,
version=1.0-SNAPSHOT, package=$groupId)
- the archetype-metadata.xml file,
- the command line options
If we go on the way defined above,
then every property will be asked.
Raphaël
2008/4/17, Arnaud HERITIER <ah...@gmail.com>:
> Same thing for me. I didn't notice it. I prefer the older behaviour.
>
> cheers
>
> arnaud
>
>
> On Thu, Apr 17, 2008 at 3:41 PM, Brian E. Fox <br...@reply.infinity.nu> 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:brett@apache.org]
> > 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
> > brett@apache.org
> > http://blogs.exist.com/bporter/
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
> >
>
>
>
>
> --
> ..........................................................
>
> 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: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: prompt behaviour changes was: [VOTE] Release Maven Archetype plugin version 2.0-alpha-3
Posted by Arnaud HERITIER <ah...@gmail.com>.
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 <br...@reply.infinity.nu> 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:brett@apache.org]
> 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
> brett@apache.org
> http://blogs.exist.com/bporter/
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
..........................................................
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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: prompt behaviour changes was: [VOTE] Release Maven Archetype plugin version 2.0-alpha-3
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
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:brett@apache.org]
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
brett@apache.org
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org