You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fop-commits@xmlgraphics.apache.org by je...@apache.org on 2005/05/24 21:45:03 UTC

cvs commit: xml-fop build.xml

jeremias    2005/05/24 12:45:03

  Modified:    .        build.xml
  Log:
  Commented the Class-Path Manifest entry which causes trouble at runtime (ClassNotFoundErrors).
  Additional infos echoed during build.
  
  Revision  Changes    Path
  1.122     +4 -1      xml-fop/build.xml
  
  Index: build.xml
  ===================================================================
  RCS file: /home/cvs/xml-fop/build.xml,v
  retrieving revision 1.121
  retrieving revision 1.122
  diff -u -r1.121 -r1.122
  --- build.xml	29 Mar 2005 19:06:08 -0000	1.121
  +++ build.xml	24 May 2005 19:45:02 -0000	1.122
  @@ -55,6 +55,7 @@
     <!-- build-local.properties is not stored in CVS and overrides values from build.properties -->
     <property file="${basedir}/build-local.properties"/>
     <property file="${basedir}/build.properties"/>
  +  <property environment="env"/>
   
     <property name="optional.lib.dir" value="${basedir}/lib"/>
   
  @@ -252,6 +253,8 @@
   
     <target name="init-avail">
       <echo message="${ant.version}"/>
  +    <echo message="VM: ${java.vm.version}, ${java.vm.vendor}"/>
  +    <echo message="JAVA_HOME: ${env.JAVA_HOME}"/>
   
       <available property="jimi.present" classname="com.sun.jimi.core.Jimi"
           classpathref="libs-build-classpath"/>
  @@ -510,7 +513,7 @@
       <jar jarfile="${build.dir}/${name}.jar" basedir="${build.dest}" includes="org/**">
         <manifest>
           <attribute name="Main-Class" value="${main.class}"/>
  -        <attribute name="Class-Path" value="${manifest-classpath}"/>
  +        <!--attribute name="Class-Path" value="${manifest-classpath}"/-->
           <attribute name="Implementation-Title" value="${Name}"/>
           <attribute name="Implementation-Version" value="${version}"/>
           <attribute name="Implementation-Vendor" value="The Apache Software Foundation (http://xml.apache.org/fop/)"/>
  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: fop-commits-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-commits-help@xmlgraphics.apache.org


Re: cvs commit: xml-fop build.xml

Posted by Jeremias Maerki <de...@greenmail.ch>.
Does anyone consider this an important feature, running FOP using "java
-jar fop.jar"? If yes, I could create a little wrapper that dynamically
sets up a classloader to load all dependencies from fop.jar's
neighbourhood. That would be a lot more flexible than the Class-Path
entry.

On 24.05.2005 21:45:03 jeremias wrote:
> jeremias    2005/05/24 12:45:03
> 
>   Modified:    .        build.xml
>   Log:
>   Commented the Class-Path Manifest entry which causes trouble at runtime (ClassNotFoundErrors).
>   Additional infos echoed during build.
>   
>   Revision  Changes    Path
>   1.122     +4 -1      xml-fop/build.xml
>   
>   Index: build.xml
>   ===================================================================
<snip/>
>          <manifest>
>            <attribute name="Main-Class" value="${main.class}"/>
>   -        <attribute name="Class-Path" value="${manifest-classpath}"/>
>   +        <!--attribute name="Class-Path" value="${manifest-classpath}"/-->
>            <attribute name="Implementation-Title" value="${Name}"/>


Jeremias Maerki