Hi Jeremias.
Jeremias Maerki:
> you might also want to take a look at how we're doing the Version.java
> thingy today:
> http://svn.apache.org/viewvc/xmlgraphics/fop/trunk/src/java/org/apache/fop/Version.java?view=markup
>
> This requires that the Manifest contains some entries standardized by
> Sun. In fop.jar this looks like this:
>
> Manifest-Version: 1.0
> Ant-Version: Apache Ant 1.6.5
> Created-By: 1.4.2_10-b03 (Sun Microsystems Inc.)
> Main-Class: org.apache.fop.cli.Main
> Build-Id: 20061106-142737-CET (Jeremias [Windows XP 5.1 x86, Java 1.4.
> 2_10-b03])
> Class-Path: avalon-framework-4.2.0.jar batik-all-1.6.jar commons-io-1.
> 1.jar commons-logging-1.0.4.jar fop-hyph.jar serializer-2.7.0.jar ser
> vlet-2.2.jar xalan-2.7.0.jar xercesImpl-2.7.1.jar xml-apis-1.3.02.jar
> xmlgraphics-commons-1.1-snapshot.jar bcprov-jdk14-130.jar bcprov-jdk
> 15-130.jar checkstyle-all-3.5.jar fop-hyph.jar fop-rfc2397.jar jai_co
> dec.jar jai_core.jar jai_imageio.jar jce-jdk13-129.jar jeuclid-1.0.ja
> r jimi-1.0.jar xmlunit1.0.jar
>
> Name: org/apache/fop/
> Specification-Title: XSL-FO - Extensible Stylesheet Language
> Specification-Version: 1.0
> Specification-Vendor: World Wide Web Consortium
> Specification-URL: http://www.w3.org/TR/xsl
> Implementation-Title: Apache FOP
> Implementation-Version: svn-trunk
> Implementation-Vendor: The Apache Software Foundation (http://xmlgraph
> ics.apache.org/fop/)
> Implementation-URL: http://xmlgraphics.apache.org/fop/
>
> "Implementation-Version" is what get's extracted. That way, you can
> control everything directly from the build process and you don't need to
> do code generation. That's just a proposal!
I’m convinced, that seems a lot simpler. I wonder whether it’d be
better to generate the manifest files from within the build.xml rather
than the files in sources/ — then these dynamic values could be created
without modifying files every build.
> It would also be good if Batik's LICENSE and NOTICE file were included
> in every JAR file under the META-INF directory. This is something that
> is being established as policy:
> http://www.apache.org/dev/release.html#what-must-every-release-contain
I thought that was only if the jars were being released separately,
outside a zip file?
--
Cameron McCormack, http://mcc.id.au/
xmpp:heycam@xxxxxxxxxx ▪ ICQ 26955922 ▪ MSN cam@xxxxxxxxx
|
