commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rahul Akolkar" <rahul.akol...@gmail.com>
Subject Re: [all] Component names for manifests
Date Sat, 05 Jan 2008 20:42:46 GMT
On 11/19/07, 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.
> >
> > 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.
>
<snip/>

Just noticed that ${project.name} affects not only the Manifest, but
also the NOTICE if the remote resources plugin is used (with defaults)
-- see Logging v1.1.1 NOTICE for example. So, if we leave these as
"Commons Foo", one more thing has to be configured (if the said plugin
is used).

-Rahul

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


Mime
View raw message