On 18/05/2009, Ceki Gulcu <c...@qos.ch> wrote: > > Hello, > > Thank you for this suggestion. Unfortunately, adding references to parent > pom, <addDefaultImplementationEntries> and > <addDefaultSpecificationEntries> creates a > manifest file which includes OSGi directives, which is really not desirable.
These can be suppressed. However, surely referencing the "apache" pom as a parent pom does not do this? I just tried, and using the "default" tags works OK for me. > 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. > http://logback.qos.ch > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
