Glen Mazza wrote:
So let me start off the voting: +1.
+1
--
Oleg Tkachenko
http://blog.tkachenko.com
Multiconn Technologies, Israel
Glen Mazza wrote:
snip/
The updates and issues he has brought up to us this
week, I'm sure he would be happy to take care of for
us, just as soon as we provide him write access. I
also hope he develops a psychological concept of
ownership of our website over time, resulting in it
looking
Glen Mazza wrote:
Team,
Waxing chutzpaic, I'd like us to try again to make
Clay a committer on this project. You may recall his
+1
(in the hope that we finally get those breadcrumbs fixed and a whole
site pdf ;-)
Christian
I know this subject has come up before, but I still cant quite get
things working after trawling through the archives.
I'm using WinCVS 1.3 and Putty to connect to the cvs.apache.org. My
understanding was that using SSH keys was optional but strongly
encouraged. So I had a go at creating the
I've had my problems with using SSH2. I finally tried SSH1 and it worked.
I suggest you create a SSH1 key pair and retry with this.
There are two ways you can work with putty. Either you create a tunnel
for CVS which has the benefit that the connection is always there as
soon as you have
Chris Bowditch wrote:
[..]
Thinking that SSH is not strictly required for write access, I had a go
Wrong!
You either need to make a frsh checkout with your commiiter id
or change your already checked out module as shown here:
http://www.apache.org/dev/committers.html#general
Christian
Jeremias Maerki wrote:
I've had my problems with using SSH2. I finally tried SSH1 and it worked.
I suggest you create a SSH1 key pair and retry with this.
Thanks for the fast response Jeremias. I have managed to get SSH1 working.
There are two ways you can work with putty. Either you create a
Chris,
I suspect that the problems with SSH2 might be to do with the way Putty
represents SSH2 keys. The format of the Putty file is different from
the openssh format, even though they contain compatible data. I think
Putty has an option to import openssh format keys, and I seem to
remember
Peter B. West wrote:
...
We could address the JVM version issue by wrapping the java.util.prefs
stuff in org.apache.fop.prefs or ...configuration classes which mimic
.util.prefs by a thin wrapper around the latter classes, and providing
for 1.3 compatible versions to be written. The
cbowditch2004/03/01 07:38:25
Modified:src/documentation/content/xdocs compliance.xml
Log:
corrected compliance for baseline-shift and vertical-align properties
Revision ChangesPath
1.25 +6 -2 xml-fop/src/documentation/content/xdocs/compliance.xml
Index:
Glen Mazza wrote:
[...]
+1
J.Pietschmann
-Original Message-
From: Clay Leeds [mailto:[EMAIL PROTECTED]
snip /
Perhaps I might even pick up a Java book and figure out how to add
command line parameters to FOP (I'm hoping I won't have to figure out
the issue that Glen and Andreas raised[1] in February, though...:-p).
Why...
gmazza 2004/03/01 15:50:26
Modified:src/java/org/apache/fop/apps Driver.java
src/java/org/apache/fop/fo FOText.java FOTreeBuilder.java
FObjMixed.java
src/java/org/apache/fop/layoutmgr AddLMVisitor.java
13 matches
Mail list logo
