You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ant.apache.org by Sam Ruby <ru...@us.ibm.com> on 2001/12/13 15:07:06 UTC
[GUMP] Build Failure - Fop
This is the first time I have seen such a failure - collisions on Ant task
names. Did something change in Ant yesterday which made the properties
file take precidence over taskdefs? Is there some way that the Ant and FOP
teams can work together to produce a combined manifest task which
satisifies all requirements?
http://cvs.apache.org/viewcvs/jakarta-ant/src/main/org/apache/tools/ant/taskdefs/Manifest.java
http://cvs.apache.org/viewcvs/xml-fop/src/org/apache/fop/tools/anttasks/Manifest.java
- Sam Ruby
---------------------- Forwarded by Sam Ruby/Raleigh/IBM on 12/13/2001
09:00 AM ---------------------------
Sam Ruby/Raleigh/IBM@IBMUS on 12/13/2001 08:55:38 AM
Please respond to fop-dev@xml.apache.org
To: fop-dev@xml.apache.org
cc:
Subject: [GUMP] Build Failure - Fop
----------------------------------------------------
This email is autogenerated from the output from:
<http://jakarta.apache.org/builds/gump/2001-12-13/xml-fop.html>
----------------------------------------------------
Buildfile: build.xml
init-avail:
init-filters-xalan2:
[copy] Copying 1 file to /home/rubys/jakarta/xml-fop/build/src/codegen
init:
[echo] ------------------- Fop 1.0dev [1999-2001] ----------------
Trying to override old definition of task manifest
prepare:
[echo] Preparing the build directories
[mkdir] Created dir:
/home/rubys/jakarta/xml-fop/build/src/org/apache/fop/fo/properties
[mkdir] Created dir:
/home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts
[mkdir] Created dir:
/home/rubys/jakarta/xml-fop/build/src/org/apache/fop/svg
[mkdir] Created dir: /home/rubys/jakarta/xml-fop/build/classes/conf
[mkdir] Created dir: /home/rubys/jakarta/xml-fop/build/classes/hyph
[copy] Copying 3 files to
/home/rubys/jakarta/xml-fop/build/classes/conf
codegen:
[echo] Resetting codegen directory
[copy] Copying 34 files to
/home/rubys/jakarta/xml-fop/build/src/codegen
[echo] Generating the java files from xml resources
[xslt] ============================
[xslt] xslt
[xslt] in: ./build/src/codegen/allprops.xml
[xslt] style: ./build/src/codegen/genconst.xsl
[xslt] out: ./build/src/org/apache/fop/fo/properties/Constants.java
[xslt] ============================
[xslt] ============================
[xslt] xslt
[xslt] in: ./build/src/codegen/foproperties.xml
[xslt] style: ./build/src/codegen/properties.xsl
[xslt] out:
./build/src/org/apache/fop/fo/properties/fo_ignore_this.java
[xslt] ============================
[xslt] ============================
[xslt] xslt
[xslt] in: ./build/src/codegen/foproperties.xml
[xslt] style: ./build/src/codegen/propmap.xsl
[xslt] out:
./build/src/org/apache/fop/fo/properties/FOPropertyMapping.java
[xslt] ============================
[xslt] ============================
[xslt] xslt
[xslt] in: ./build/src/codegen/foproperties.xml
[xslt] style: ./build/src/codegen/enumgen.xsl
[xslt] out:
./build/src/org/apache/fop/fo/properties/foenums_ignore_this.java
[xslt] ============================
[xslt] ============================
[xslt] xslt
[xslt] in: ./build/src/codegen/charlist.xml
[xslt] style: ./build/src/codegen/code-point-mapping.xsl
[xslt] out:
./build/src/org/apache/fop/render/pdf/CodePointMapping.java
[xslt] ============================
[xslt] ============================
[xslt] xslt
[xslt] in: ./build/src/codegen/Courier.xml
[xslt] style: ./build/src/codegen/font-file.xsl
[xslt] out: ./build/src/org/apache/fop/render/pdf/fonts/Courier.java
[xslt] ============================
[xslt] ============================
[xslt] xslt
[xslt] in: ./build/src/codegen/Courier-Oblique.xml
[xslt] style: ./build/src/codegen/font-file.xsl
[xslt] out:
./build/src/org/apache/fop/render/pdf/fonts/CourierOblique.java
[xslt] ============================
[xslt] ============================
[xslt] xslt
[xslt] in: ./build/src/codegen/Courier-Bold.xml
[xslt] style: ./build/src/codegen/font-file.xsl
[xslt] out:
./build/src/org/apache/fop/render/pdf/fonts/CourierBold.java
[xslt] ============================
[xslt] ============================
[xslt] xslt
[xslt] in: ./build/src/codegen/Courier-BoldOblique.xml
[xslt] style: ./build/src/codegen/font-file.xsl
[xslt] out:
./build/src/org/apache/fop/render/pdf/fonts/CourierBoldOblique.java
[xslt] ============================
[xslt] ============================
[xslt] xslt
[xslt] in: ./build/src/codegen/Helvetica.xml
[xslt] style: ./build/src/codegen/font-file.xsl
[xslt] out: ./build/src/org/apache/fop/render/pdf/fonts/Helvetica.java
[xslt] ============================
[xslt] ============================
[xslt] xslt
[xslt] in: ./build/src/codegen/Helvetica-Oblique.xml
[xslt] style: ./build/src/codegen/font-file.xsl
[xslt] out:
./build/src/org/apache/fop/render/pdf/fonts/HelveticaOblique.java
[xslt] ============================
[xslt] ============================
[xslt] xslt
[xslt] in: ./build/src/codegen/Helvetica-Bold.xml
[xslt] style: ./build/src/codegen/font-file.xsl
[xslt] out:
./build/src/org/apache/fop/render/pdf/fonts/HelveticaBold.java
[xslt] ============================
[xslt] ============================
[xslt] xslt
[xslt] in: ./build/src/codegen/Helvetica-BoldOblique.xml
[xslt] style: ./build/src/codegen/font-file.xsl
[xslt] out:
./build/src/org/apache/fop/render/pdf/fonts/HelveticaBoldOblique.java
[xslt] ============================
[xslt] ============================
[xslt] xslt
[xslt] in: ./build/src/codegen/Times-Roman.xml
[xslt] style: ./build/src/codegen/font-file.xsl
[xslt] out:
./build/src/org/apache/fop/render/pdf/fonts/TimesRoman.java
[xslt] ============================
[xslt] ============================
[xslt] xslt
[xslt] in: ./build/src/codegen/Times-Italic.xml
[xslt] style: ./build/src/codegen/font-file.xsl
[xslt] out:
./build/src/org/apache/fop/render/pdf/fonts/TimesItalic.java
[xslt] ============================
[xslt] ============================
[xslt] xslt
[xslt] in: ./build/src/codegen/Times-Bold.xml
[xslt] style: ./build/src/codegen/font-file.xsl
[xslt] out: ./build/src/org/apache/fop/render/pdf/fonts/TimesBold.java
[xslt] ============================
[xslt] ============================
[xslt] xslt
[xslt] in: ./build/src/codegen/Times-BoldItalic.xml
[xslt] style: ./build/src/codegen/font-file.xsl
[xslt] out:
./build/src/org/apache/fop/render/pdf/fonts/TimesBoldItalic.java
[xslt] ============================
[xslt] ============================
[xslt] xslt
[xslt] in: ./build/src/codegen/ZapfDingbats.xml
[xslt] style: ./build/src/codegen/font-file.xsl
[xslt] out:
./build/src/org/apache/fop/render/pdf/fonts/ZapfDingbats.java
[xslt] ============================
[xslt] ============================
[xslt] xslt
[xslt] in: ./build/src/codegen/Symbol.xml
[xslt] style: ./build/src/codegen/font-file.xsl
[xslt] out: ./build/src/org/apache/fop/render/pdf/fonts/Symbol.java
[xslt] ============================
prepare-jimi:
prepare-jai:
prepare-trax:
[echo] JAXP1.1 transforms is present. Installing TRaX support
[copy] Copying 3 files to /home/rubys/jakarta/xml-fop/build/src
prepare-src:
[copy] Copying 458 files to /home/rubys/jakarta/xml-fop/build/src
compile:
[echo] Compiling the sources
[mkdir] Created dir:
/home/rubys/jakarta/xml-fop/build/classes/org/apache/fop/viewer/resources
[copy] Copying 9 files to
/home/rubys/jakarta/xml-fop/build/classes/org/apache/fop/viewer/resources
[mkdir] Created dir:
/home/rubys/jakarta/xml-fop/build/classes/org/apache/fop/viewer/Images
[copy] Copying 5 files to
/home/rubys/jakarta/xml-fop/build/classes/org/apache/fop/viewer/Images
[javac] Compiling 773 source files to
/home/rubys/jakarta/xml-fop/build/classes
[javac] Note:
/home/rubys/jakarta/xml-fop/build/src/org/apache/fop/tools/anttasks/CompileXMLFiles.java
uses or overrides a deprecated API. Recompile with "-deprecation" for
details.
[javac] 1 warning
hyphenation:
[serHyph] Processing ./hyph/de_DR.xml
[serHyph] Processing ./hyph/da.xml
[serHyph] Processing ./hyph/de.xml
[serHyph] Processing ./hyph/en_GB.xml
[serHyph] Processing ./hyph/en.xml
[serHyph] Processing ./hyph/en_US.xml
[serHyph] Processing ./hyph/es.xml
[serHyph] Processing ./hyph/fi.xml
[serHyph] Processing ./hyph/fr.xml
[serHyph] Processing ./hyph/it.xml
[serHyph] Processing ./hyph/nl.xml
[serHyph] Processing ./hyph/no.xml
[serHyph] Processing ./hyph/ru.xml
[serHyph] Processing ./hyph/sk.xml
[serHyph] Processing ./hyph/pl.xml
package:
[echo] Creating the jar file ./build/fop.jar
BUILD FAILED
/home/rubys/jakarta/xml-fop/build.xml:501: Class
org.apache.tools.ant.taskdefs.Manifest doesn't support the "overwrite"
attribute.
Total time: 7 minutes 55 seconds
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [GUMP] Build Failure - Fop
Posted by Keiron Liddle <ke...@aftexsw.com>.
On 2001.12.13 15:07 Sam Ruby wrote:
> This is the first time I have seen such a failure - collisions on Ant
> task
> names. Did something change in Ant yesterday which made the properties
> file take precidence over taskdefs? Is there some way that the Ant and
> FOP
> teams can work together to produce a combined manifest task which
> satisifies all requirements?
We can update the FOP build to use the core ant manifest task and a new
ant.
This is no real problem.
The only thing that our task does that is different is a "BUILD-ID" it has
"Date-Time (user@host [os])".
It probably is not really important.
It would good to simply use the ant tasks rather than having our own ones.
How stable are these tasks and any other new tasks.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [GUMP] Build Failure - Fop
Posted by Keiron Liddle <ke...@aftexsw.com>.
On 2001.12.13 15:07 Sam Ruby wrote:
> This is the first time I have seen such a failure - collisions on Ant
> task
> names. Did something change in Ant yesterday which made the properties
> file take precidence over taskdefs? Is there some way that the Ant and
> FOP
> teams can work together to produce a combined manifest task which
> satisifies all requirements?
We can update the FOP build to use the core ant manifest task and a new
ant.
This is no real problem.
The only thing that our task does that is different is a "BUILD-ID" it has
"Date-Time (user@host [os])".
It probably is not really important.
It would good to simply use the ant tasks rather than having our own ones.
How stable are these tasks and any other new tasks.
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: [GUMP] Build Failure - Fop
Posted by Stefan Bodewig <bo...@apache.org>.
Sam,
could you please try the attached patch? It is far from perfect and
won't help with tasks that are inside "TaskContainer"s but is a first
cut.
I cannot find a sensible way to replace existing task objects inside
TaskContainers without adding a getTasks method to TaskContainer,
which I wouldn't like to do. Others?
Stefan
Index: src/main/org/apache/tools/ant/Target.java
===================================================================
RCS file: /home/cvs/jakarta-ant/src/main/org/apache/tools/ant/Target.java,v
retrieving revision 1.29
diff -u -r1.29 Target.java
--- src/main/org/apache/tools/ant/Target.java 2001/12/12 09:17:36 1.29
+++ src/main/org/apache/tools/ant/Target.java 2001/12/13 16:17:11
@@ -178,11 +178,38 @@
public void execute() throws BuildException {
if (testIfCondition() && testUnlessCondition()) {
- Enumeration enum = children.elements();
- while (enum.hasMoreElements()) {
- Object o = enum.nextElement();
+ for (int i=0; i<children.size(); i++) {
+ Object o = children.elementAt(i);
if (o instanceof Task) {
Task task = (Task) o;
+
+ String elementName = task.taskType;
+ Class currentTaskClass = null;
+ if (o instanceof TaskAdapter) {
+ currentTaskClass = ((TaskAdapter) o).getProxy().getClass();
+ } else {
+ currentTaskClass = task.getClass();
+ }
+
+ Class validTaskClass =
+ (Class) project.getTaskDefinitions().get(elementName);
+ if (!(o instanceof UnknownElement)
+ && !currentTaskClass.equals(validTaskClass)) {
+ project.log("replacing task "+elementName+" at "+task.getLocation()+". Old class: "+currentTaskClass+", new class "+validTaskClass,
+ Project.MSG_VERBOSE);
+
+ Task newTask = project.createTask(elementName);
+ newTask.setLocation(task.getLocation());
+ newTask.setOwningTarget(this);
+ children.setElementAt(newTask, i);
+ newTask.init();
+ RuntimeConfigurable wrapper =
+ task.getRuntimeConfigurableWrapper();
+ newTask.setRuntimeConfigurableWrapper(wrapper);
+ wrapper.setProxy(newTask);
+ task = newTask;
+ }
+
task.perform();
} else {
RuntimeConfigurable r = (RuntimeConfigurable) o;
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [GUMP] Build Failure - Fop
Posted by Stefan Bodewig <bo...@apache.org>.
I think I know what's going on, but I don't have all pieces together
to test it (yet) - does it work if you move the <taskdef> for FOP's
manifest task out of the target and make it a sibling of target?
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: [GUMP] Build Failure - Fop
Posted by Stefan Bodewig <bo...@apache.org>.
I think I know what's going on, but I don't have all pieces together
to test it (yet) - does it work if you move the <taskdef> for FOP's
manifest task out of the target and make it a sibling of target?
Stefan
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [GUMP] Build Failure - Fop
Posted by Stefan Bodewig <bo...@apache.org>.
A quick fix, change the package target to
<target name="package" depends="compile,hyphenation">
<echo message="Creating the jar file ${build.dir}/${name}.jar"/>
<jar jarfile="${build.dir}/${name}.jar"
basedir="${build.dest}"
includes="org/**,conf/**,hyph/**">
<manifest>
<attribute name="Main-Class" value="${main.class}" />
<attribute name="Class-Path" value=""${runtime.classpath}" />
<attribute name="Implementation-Title" value="${Name}" />
<attribute name="Implementation-Version" value="${version}" />
<attribute name="Implementation-Vendor" value="Apache Software Foundation (http://xml.apache.org/fop/)"/>
</manifest>
</jar>
</target>
this will work with Ant 1.4 and later. Still looking into the other
issues.
Stefan
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [GUMP] Build Failure - Fop
Posted by Stefan Bodewig <bo...@apache.org>.
A quick fix, change the package target to
<target name="package" depends="compile,hyphenation">
<echo message="Creating the jar file ${build.dir}/${name}.jar"/>
<jar jarfile="${build.dir}/${name}.jar"
basedir="${build.dest}"
includes="org/**,conf/**,hyph/**">
<manifest>
<attribute name="Main-Class" value="${main.class}" />
<attribute name="Class-Path" value=""${runtime.classpath}" />
<attribute name="Implementation-Title" value="${Name}" />
<attribute name="Implementation-Version" value="${version}" />
<attribute name="Implementation-Vendor" value="Apache Software Foundation (http://xml.apache.org/fop/)"/>
</manifest>
</jar>
</target>
this will work with Ant 1.4 and later. Still looking into the other
issues.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: [GUMP] Build Failure - Fop
Posted by Stefan Bodewig <bo...@apache.org>.
On Thu, 13 Dec 2001, Sam Ruby <ru...@us.ibm.com> wrote:
> Did something change in Ant yesterday which made the properties file
> take precidence over taskdefs?
No, at least not yesterday. What has changed yesterday is that we've
added a new task named manifest, so there simply hasn't been any
collision before that.
> Is there some way that the Ant and FOP teams can work together to
> produce a combined manifest task which satisifies all requirements?
Ant's manifest task can do all things FOP's does, AFAICS. You'd have
to replace the attributes with nested <attribute> elements and
explicit names, that's all. On the other hand, this would make FOP's
build process depend on an unreleased version of Ant.
I'll try to see why Ant's task definition takes precedence, because it
shouldn't be that way. Thanks for the heads-up.
Stefan
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [GUMP] Build Failure - Fop
Posted by Stefan Bodewig <bo...@apache.org>.
On Thu, 13 Dec 2001, Sam Ruby <ru...@us.ibm.com> wrote:
> Did something change in Ant yesterday which made the properties file
> take precidence over taskdefs?
No, at least not yesterday. What has changed yesterday is that we've
added a new task named manifest, so there simply hasn't been any
collision before that.
> Is there some way that the Ant and FOP teams can work together to
> produce a combined manifest task which satisifies all requirements?
Ant's manifest task can do all things FOP's does, AFAICS. You'd have
to replace the attributes with nested <attribute> elements and
explicit names, that's all. On the other hand, this would make FOP's
build process depend on an unreleased version of Ant.
I'll try to see why Ant's task definition takes precedence, because it
shouldn't be that way. Thanks for the heads-up.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org