[
https://issues.apache.org/jira/browse/OFBIZ-5169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13623553#comment-13623553
]
Jacopo Cappellato commented on OFBIZ-5169:
------------------------------------------
Adrian,
I think that gathering information from a profiler would indeed help.
However, would it make sense, if there is a general agreement, to create a
branch with the current trunk to keep a Javolution version of OFBiz and then
commit the changes to remove Javolution (after your review/tests) to the trunk?
I am basically saying that we could use the branch the other way round: in the
future we could use it to run comparisons with the Javolution-free trunk.
A TAG would also probably work (because the Javolution branch will be mostly
read-only) but a branch may give us some flexibility: for example we could
commit there some optimizations done in the trunk that are not related to
Javolution and that may impact performance.
In this way it will be easier to migrate out of Javolution in steps.
Of course before doing this we should check with the community if there are
still major concerns.
> Removing Javolution from framework components
> ---------------------------------------------
>
> Key: OFBIZ-5169
> URL: https://issues.apache.org/jira/browse/OFBIZ-5169
> Project: OFBiz
> Issue Type: Improvement
> Components: framework
> Affects Versions: SVN trunk
> Reporter: Varun Bhansaly
> Priority: Minor
> Fix For: SVN trunk
>
> Attachments: framework-FastList-removed.patch
>
>
> a. Remove static instances of Javolution objects.
> b. Remove other uses of Javolution objects.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
