Is HEAD supposed to be compiling? I'm getting errors starting at
datatypes/ColorType.java.
Peter
--
Peter B. West http://www.powerup.com.au/~pbwest/resume.html
Recent commits to alt-design have laid the groundwork for handling of
fo:marker within fo:static-content.
...xml.SyncedXmlEventsBuffer now extends
...datastructs.SyncedCircularBuffer and implements
...xml.XmlEventSource. A new class, ...xml.XmlEventsArrayBuffer, also
implements
Finn Bock wrote:
I have not yet removed the properties.xsl file from CVS. I guess it
should be removed since it isn't used anymore.
[J.Pietschmann]
I think you could leave the file there for now.
Ok.
It should be
sufficient to inactivate the related task in the buildfile
(for example
[Peter B. West]
Is HEAD supposed to be compiling?
Yes. I can compile it just fine from a fresh checkout.
I'm getting errors starting at datatypes/ColorType.java.
Which errors? Have you tried to do a ant clean first?
regards,
finn
The ASF does see a problem. Until the FSF has clarified the relationship
between linking and Java's import concept the ASF's policy is not to
allow usage of LGPL packages. There are certain exceptions. For example,
if you have a JAI-compatible image codec under the LPGL you could use it
because
On 21.01.2004 15:34:15 Glen Mazza wrote:
--- Peter B. West [EMAIL PROTECTED] wrote:
It seems to me that a major motivation for writing
OSS is precisely the
recognition. When alt-design is completed, I will
probably have written
the bulk of it, as well as designing it, and I have
pbwest 2004/01/23 04:47:58
Modified:src/java/org/apache/fop/fo Tag: FOP_0-20-0_Alt-Design
FoRoot.java
Log:
Remove pageSequenceMasters HashMap.
Add LayoutMasterSet to FoPageSequence constructor.
Revision ChangesPath
No revision
pbwest 2004/01/23 04:52:23
Modified:src/java/org/apache/fop/fo/flow Tag: FOP_0-20-0_Alt-Design
FoPageSequence.java
Log:
Added LayoutMasterSet to constructor.
Changed name of the index of the fo:flow child to flowChild.
Revision ChangesPath
No
Does anyone know why we wrap the datatypes instances
in a property
instance? I think we could avoid the property
instance by having the
datatypes extends an AbstractProperty class which
implement a Property
interface:
[Glen Mazza]
Could you explain why we have the datatypes instances
to begin
jeremias2004/01/23 07:07:29
Modified:.build.xml
Log:
Fixed a bug where I got a NoClassDefFoundError when I'm using a
build-local.properties where I set optional.lib.dir to an absolute Windows path. These
absolute paths weren't removed somehow resulting in NoClassDefFound
Hi Jeremias,
thanks for the quick response.
Jeremias Maerki wrote:
The ASF does see a problem. Until the FSF has clarified the relationship
between linking and Java's import concept the ASF's policy is not to
allow usage of LGPL packages. There are certain exceptions. For example,
if you have a
No apologies required!
Image IO (javax.imageio) support is not there, yet, I'm afraid. But if
you created an implementation for Image IO then your idea would work.
Shouldn't be very hard. Check the org.apache.fop.image package. You
wouldn't need to use JIMI. Think of JIMI, JAI and ImageIO as
bckfnn 2004/01/23 13:39:59
Modified:src/java/org/apache/fop/fo BorderWidthPropertyMaker.java
BoxPropShorthandParser.java
CompoundPropertyMaker.java
GenericShorthandParser.java
13 matches
Mail list logo
