The current behaviour is that goals are public, so I'd much prefer we kept the existing behavour, and the default was public="true". -- dIon Gillard, Multitask Consulting Blog: http://blogs.codehaus.org/people/dion/
"Vincent Massol" <[EMAIL PROTECTED]> wrote on 01/09/2003 04:55:41 PM: > > > > -----Original Message----- > > From: Brett Porter [mailto:[EMAIL PROTECTED] > > Sent: 01 September 2003 07:36 > > To: 'Maven Developers List' > > Subject: RE: plugin version upgrading/downgrading > > > > > What about making the goal public when it has a description > > > element defined? I had reported a bug (dunno if it had been > > > fixed) where currently the "maven -g" displays "null" as the > > > description for non-public goals (i.e. those that have no > > > description). I believe it was implemented like this in the > > > past and someone modified it... > > > > I fixed that bug so it works again now. The publicity bug I think is > still > > open. > > > > Basing the publicity on description feels like too much of a side > effect. > > I > > think the namespace idea is clearer if it works. I'm all for requiring > a > > description for public goals though. > > I think the namespace also looks like a kludge! If we change things we'd > better make it right this time, don't you think? :-) > > What about introducing an attribute on the <goal> element? Like "public" > for example? > > <goal name="cactus:whatever" public="true"> > [...] > > By default, a goal would be private. > > -Vincent > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
