, at 2:33 PM, Vince Bonfanti wrote:
I'm trying to run the HTTP and Webdav testcases without any of my changes
in
order to verify my test environment. I'm running on CentOS 5.3 with the
built-in Apache 2.2 server. I believe I've followed the instructions
properly, but I'm getting two errors
?
On Mon, Jun 22, 2009 at 2:43 PM, Vince Bonfanti vbonfa...@gmail.com wrote:
I fixed the HTTP failure by disabling the welcome page in welcome.conf (I
don't know if this is standard Apache configuration or something peculiar to
CentOS). All of the HTTP tests are now passing with my changes
I'm trying to run the HTTP and Webdav testcases without any of my changes in
order to verify my test environment. I'm running on CentOS 5.3 with the
built-in Apache 2.2 server. I believe I've followed the instructions
properly, but I'm getting two errors. I'm going to give up for now and try
again
that the functional
tests that require external servers also pass - if you do a mvn site:stage
you will see the documentation on how to do that.
VFS-245 is opened against AbstractFileName and probably needs to be dealt
with in the context of what you are doing.
On Jun 4, 2009, at 2:22 PM, Vince Bonfanti
Got it. I'll start working on this tomorrow. Thanks.
On Thu, Jun 18, 2009 at 5:39 PM, ralph.goers @dslextreme.com
ralph.go...@dslextreme.com wrote:
And after you run mvn site they should show up in target/site/testing.html.
Setting MAVEN_OPTS=-Xmx512m did the trick. Thanks.
On Thu, Jun 18, 2009 at 3:19 PM, Siegfried Goeschl
siegfried.goes...@it20one.at wrote:
Hi Vince,
when you check your mvn script there is a 'MAVEN_OPTS' environment
variable - here you can increase your memory settings for M2 by setting
a
I've added a patch file with a proposed fix to VFS-245.
On Thu, Jun 4, 2009 at 6:40 PM, Ralph Goers ralph.go...@dslextreme.comwrote:
VFS-245 is opened against AbstractFileName and probably needs to be dealt
with in the context of what you are doing.
I'm investigating creating a memcached-based FilesCache implementation for
use with Google App Engine. The basic obstacle is that this requires that
all objects that are used as keys or values must be serializable. Before I
go too far down this path, I'd like to know if this is a reasonable thing
There are two reasons for this:
1. GAE does not set the os.arch or os.version system properties.
When Commons VFS initializes, it tries to do this (OS.java line 36), which
throws NullPointerExceptions:
* private* *static* *final* String *OS_ARCH* = System.*getProperty*(
:
On May 30, 2009, at 2:55 PM, Vince Bonfanti wrote:
The first public release (0.1) of GaeVFS is now available:
http://gaevfs.appspot.com/
GaeVFS is a plug-in for Apache Commons VFS that implements a virtual file
system on top of the Google App Engine for Java (GAE) datastore. It
provides
The first public release (0.1) of GaeVFS is now available:
http://gaevfs.appspot.com/
GaeVFS is a plug-in for Apache Commons VFS that implements a virtual file
system on top of the Google App Engine for Java (GAE) datastore. It provides
a writeable file system for GAE, since GAE does not
My code will always run within a servlet, so I can close() the filesystem
when the servlet is destroyed. In this case, I should be OK using
LRUFilesCache?
Thanks,
Vince
On Tue, May 26, 2009 at 2:28 AM, Mario Ivankovits ma...@ops.co.at wrote:
Hi!
1. Is the LRUFilesCache safe for production
I'm working on a Google App Engine/Java (GAE/J) plug-in for VFS (it's almost
done) and have a few questions:
1. Is the LRUFilesCache safe for production use? GAE/J won't allow using
the default SoftRefFilesCache because it doesn't allow background threads.
I've found a few really old messages
13 matches
Mail list logo
