Re: Compile error in HEAD

2004-01-11 Thread Simon Pepping
Glen, On Sat, Jan 10, 2004 at 01:54:35PM -0800, Glen Mazza wrote: > Simon, > > I can't duplicate the problem on my machine but I > think I see the issue: there is *no* more > org.apache.fop.fo.properties.Constants interface > anymore, it's been gone for a month or so. I think > you just need to

Re: Compile error in HEAD

2004-01-10 Thread Glen Mazza
--- Glen Mazza <[EMAIL PROTECTED]> wrote: > > Yes, but the Eclipse warnings of "unneeded imports" > drives Peter West and a few others crazy. If the > above does not work, our only other solution would > be > a fully qualified import statement. > oops...I mean "fully qualifying the Constants va

Re: Compile error in HEAD

2004-01-10 Thread Glen Mazza
--- Simon Pepping <[EMAIL PROTECTED]> wrote: > > The cause is that the import section is not > sufficient: > > package org.apache.fop.fo.properties; > > import org.apache.fop.fo.*; > import org.apache.fop.apps.FOPException; > > With these import statements the compiler applies > interface

Compile error in HEAD

2004-01-10 Thread Simon Pepping
Hi, The code that I checked out this evening from CVS HEAD generates compile errors, for example, [javac] /fsd/source/xml-fop/build/gensrc/org/apache/fop/fo/properties/BorderBottomStyleMaker.java:21: cannot resolve symbol [javac] symbol : variable PR_BORDER_AFTER_STYLE [javac] loc