I was thinking a general workflow might be:
1. Work on framework components first.
a. Remove static instances of Javolution objects.
b. Remove other uses of Javolution objects.
2. Work on application components.
3. Work on special purpose, themes, etc last.
4. Run memory-use and performance tests.
-Adrian
On 3/29/2013 12:00 PM, Varun Bhansaly wrote:
Let me know your ideas or where/ what to start with and I will submitting
patches in JIRA.
On 29 Mar 2013 17:27, "Adrian Crum" <[email protected]>
wrote:
Cool - thanks!
https://svn.apache.org/repos/**asf/ofbiz/branches/2013_**RemoveJavolution<https://svn.apache.org/repos/asf/ofbiz/branches/2013_RemoveJavolution>
-Adrian
On 3/29/2013 11:46 AM, Varun Bhansaly wrote:
Hi Adrian,
I would like help on this one.
On 29 Mar 2013 16:58, "Adrian Crum"
<adrian.crum@sandglass-**software.com<[email protected]>
wrote:
A discussion from about a year ago:
http://mail-archives.apache.****org/mod_mbox/ofbiz-dev/201205.****
mbox/%3C42B94A35-C72F-4C83-****8E7E-FC97FB37DDB1@hotwaxmedia.****com%3E<
http://mail-archives.**apache.org/mod_mbox/ofbiz-dev/**
201205.mbox/%3C42B94A35-C72F-**4C83-8E7E-FC97FB37DDB1@**
hotwaxmedia.com%3E<http://mail-archives.apache.org/mod_mbox/ofbiz-dev/201205.mbox/%[email protected]%3E>
I can create a branch and start working on this. Does anyone want to
help?
-Adrian
