commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ceki Gulcu <>
Subject Re: commons-logging version 0.0.0-EMPTY
Date Mon, 18 May 2009 16:47:19 GMT


Thank you for this suggestion. Unfortunately, adding references to parent pom, 
<addDefaultImplementationEntries> and <addDefaultSpecificationEntries> creates
manifest file which includes OSGi directives, which is really not desirable.

I changed the contents of the name element to "Commons Logging".

sebb wrote:
> Thanks, although IMO it would have been better to use
>             <manifest>
>               <addDefaultImplementationEntries>true</addDefaultImplementationEntries>
>               <addDefaultSpecificationEntries>true</addDefaultSpecificationEntries>
>             </manifest>
> rather than hard-coding the values.
> Also, the pom <name> is wrong, it should be
>   <name>Commons Logging</name>
> as per the existing pom.xml in logging/trunk.
> The pom.xml for empty_logging should also have as parent either the
> commons parent, or at least the apache parent.
> That would allow the use of the default manifest entries as above.

Ceki Gülcü
Logback: The reliable, generic, fast and flexible logging framework for Java.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message