On 02/20/2013 09:33 PM, Oliver Heger wrote: > Am 20.02.2013 16:42, schrieb t...@apache.org: >> Author: tn >> Date: Wed Feb 20 15:42:09 2013 >> New Revision: 1448251 >> >> URL: http://svn.apache.org/r1448251 >> Log: >> Update version info >> >> Modified: >> commons/proper/logging/trunk/src/conf/MANIFEST.MF >> >> Modified: commons/proper/logging/trunk/src/conf/MANIFEST.MF >> URL: >> http://svn.apache.org/viewvc/commons/proper/logging/trunk/src/conf/MANIFEST.MF?rev=1448251&r1=1448250&r2=1448251&view=diff >> >> ============================================================================== >> >> --- commons/proper/logging/trunk/src/conf/MANIFEST.MF (original) >> +++ commons/proper/logging/trunk/src/conf/MANIFEST.MF Wed Feb 20 >> 15:42:09 2013 >> @@ -5,4 +5,4 @@ Specification-Version: 1.0 >> Implementation-Title: Commons Logging >> Implementation-Vendor-Id: org.apache >> Implementation-Vendor: Apache Software Foundation >> -Implementation-Version: 1.1.1 >> +Implementation-Version: 1.1.2 >> >> > Just wondering whether this is necessary. Doesn't the maven build > automatically generate a fully configured MANIFEST including OSGi meta > data?
yes, but somehow the ant build script is still in use (e.g. for gump) and both ant & maven refer to this hard-coded manifest. Thomas --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
