Hi Simon,
Simon Kitching wrote on Friday, January 20, 2006 10:01 AM:
[snip]
> commons-logging doesn't use maven to build the jars (only the site).
>
> <jar jarfile="${build.home}/${core.jar.name}"
> basedir="${build.home}/classes"
> manifest="${build.home}/conf/MANIFEST.MF">
> <include name="org/apache/commons/logging/**" />
> <include name="META-INF/LICENSE.txt"/>
> <include name="META-INF/NOTICE.txt"/>
> <exclude name="**/package.html"/>
> </jar>
>
> The currently generated manifest is:
>
> Manifest-Version: 1.0
> Ant-Version: Apache Ant 1.6.5
> Created-By: 1.5.0_04-b05 (Sun Microsystems Inc.)
> Extension-Name: org.apache.commons.logging
> Specification-Vendor: Apache Software Foundation
> Specification-Version: 1.0
> Implementation-Vendor: Apache Software Foundation
> Implementation-Version: 1.1
>
>
> Do you know if there's anything extra needed?
Well, it just claims, that 1.1 is still compatible to 1.0 regarding API and
spec. Cannot say, if this is really true, you're the expert here :) Possibly a
clirr report against JCL-1.0 will tell. Otherwise it looks good. You might add
an (optional) Specification-Title though:
Specification-Title: "Jakarta Commons Logging"
- Jörg
BTW: Can you still use the resulting jar with 1.3? Just because it was build
with 1.5 ...
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
