commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sebb <seb...@gmail.com>
Subject Re: [all] Component names for manifests
Date Mon, 19 Nov 2007 19:39:58 GMT
On 19/11/2007, Niall Pemberton <niall.pemberton@gmail.com> wrote:
> On Nov 19, 2007 5:58 PM, Rahul Akolkar <rahul.akolkar@gmail.com> wrote:
> > New thread:
> >
> > >> Dennis Lundberg wrote:
> > > <snip/>
> > >>> I'll change this. Should it be changed to "Apache Commons Logging"
or
> > >>> simply "Commons Logging"? This is what we currently have:
> > >>>
> > >>> Specification-Title: Jakarta Commons Logging
> > >>> Specification-Vendor: Apache Software Foundation
> > >> I had a look at what was in the jars where the manifest was produced by
> > >> Maven. These use ${project.name} for this, so I'll go with "Commons
> > >> Logging" here.
> > >>
> > > <snap/>
> > >
> > > I think we should consider updating ${project.name}s to Apache Commons
> > > Foo then.

If it's not clear whether or not an existing property is suitable,
then rather than changing an existing one, perhaps create a dedicated
one?

> >
> > Thoughts?
>
> My preference is we stick with "Commons Foo" rather than "Apache
> Commons Foo" which is more of a mouthfull. Specifically for the
> manifest since we have "Vendor" entries which say "Apache Software
> Foundation" then IMO duplicating it in the "Title" entries makes no
> sense to me.

+1

> Niall
>
> > -Rahul
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Mime
View raw message