Good ideas are welcome, as ever simply contribute patches in a Jira. Of course against trunk is highly preferred. Often an example
is enough to show the way for those interested, more chances than just a message in the dev ML...
Jacques
From: BJ Freeman bjf...@free-man.net
add links to the
Why not try to increase maxmemory? 512 sounnds good to me
Jacques
From: mrisal...@libero.it
Hi dev,
I have done some changes to make working the creation of javadoc documentation
during buildbot (step 4) and now there are no more any warning and the step is
now green on buildbot.
On my
[
https://issues.apache.org/jira/browse/OFBIZ-3784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13044292#comment-13044292
]
Jacques Le Roux commented on OFBIZ-3784:
Reverted at r1131396, see All tabs for
[
https://issues.apache.org/jira/browse/OFBIZ-3784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13044293#comment-13044293
]
Jacques Le Roux commented on OFBIZ-3784:
BTW Sascha,
I guess you added this
The Buildbot has detected a new failure on builder ofbiz-trunk while building
ASF Buildbot.
Full details are available at:
http://ci.apache.org/builders/ofbiz-trunk/builds/1857
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: isis_ubuntu
Build Reason: scheduler
Build Source
Hi all,
Can anyone help me to understand the coding of the
applications/accounting/build.xml which will be a great help me to continue
on my works.
Also I change the module structure as src/ to src/main/java where we need to
do the changes?
--
thanks
Ganath
So from what I can tell the ttl works fine on the testExpire test case but the
call to useAllMemory() doesn't successfully cause the cache to be cleared. I'm
guessing it works fine locally because our systems are slower that the test
server and the other startup threads running cause the ttl
