Title: Message
Hi David
 
I think you've found a problem with the current Ant build file - the source & binary distribution does not include the manifest file in it. I've just fixed the build process which should fix this problem. You can try using the daily build which should have the problem resolved.
 
An alternative is to take a snapshot from CVS and build that instead. Hopefully this will be fixed in the next major release shortly.

James
----- Original Message -----
Sent: Tuesday, October 09, 2001 4:31 PM
Subject: [dom4j-user] dom4j 1.0 build failure...

Any ideas??
 
-------
 
 
C:\local\dom4j-1.0>build
Buildfile: build.xml
 
init:
     [echo] ----------- dom4j 1.0 [2001] ------------
 
clean:
 
prepare:
    [mkdir] Created dir: C:\local\dom4j-1.0\build
 
prepare-src:
    [mkdir] Created dir: C:\local\dom4j-1.0\build\src
    [mkdir] Created dir: C:\local\dom4j-1.0\build\classes
     [copy] Copying 197 files to C:\local\dom4j-1.0\build\src
 
collections:
 
compile:
    [javac] Compiling 197 source files to C:\local\dom4j-1.0\build\classes
    [javac] Note: sun.tools.javac.Main has been deprecated.
    [javac] 1 warning
 
package:
    [unjar] Expanding: C:\local\dom4j-1.0\lib\saxpath.jar into C:\local\dom4j-1.0\build\classes
    [unjar] Expanding: C:\local\dom4j-1.0\lib\jaxen.jar into C:\local\dom4j-1.0\build\classes
   [delete] Deleting directory C:\local\dom4j-1.0\build\classes\META-INF
      [jar] Building jar: C:\local\dom4j-1.0\build\dom4j-core.jar
 
BUILD FAILED
 
C:\local\dom4j-1.0\build.xml:211: Manifest file: C:\local\dom4j-1.0\src\conf\MANIFEST.MF does not exist.
 
Total time: 20 seconds
C:\local\dom4j-1.0>

Reply via email to