[jira] Commented: (GERONIMO-2995) Weed out backport-util-concurrent usage for server/trunk

["Jason Dillon (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/GERONIMO-2995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482346 ] 

Jason Dillon commented on GERONIMO-2995:
----------------------------------------

This is *mostly* done... we still need to include backport for rmi-naming and client configs, mostly due to {{org.apache.geronimo.gjndi.GlobalContextGBean}} I believe, though I'm not sure where that comes from so I can't update it at the moment.

2 non-import/pom changes were needed due to minor incompatibilities:

ConcurrentHashMap(int initialCapacity, float loadFactor) does not exist, using ConcurrentHashMap(int initialCapacity) since we were using the default loadFactory of {{0.75f}} anyways.

TimeUnit.MINUTES does not exist... use TimeUnit.SECONDS and multiply timed value by 60 to get minutes.

> Weed out backport-util-concurrent usage for server/trunk
> --------------------------------------------------------
>
>                 Key: GERONIMO-2995
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-2995
>             Project: Geronimo
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>    Affects Versions: 2.0
>            Reporter: Jason Dillon
>         Assigned To: Jason Dillon
>
> Now that server/trunk requires 1.5 to build and run, I think we should start to weed out our usage of the {{backport-util-concurrent}} library (and concurrent if there is still anything left of that in our src tree).
> I think we may still have to include {{backport-util-concurrent-\*.jar}} in the assembly until all of our dependencies have weeded it out too... or perhaps just have to live with that in the repository.  But hopefully we can remove our usage of these classes and not need to include this puppy in {{lib/\*}} anymore.
> Looks like we are currently using {{edu.emory.mathcs.backport}} in 39 locations (based on imports) which are over 25 files.
> Even after weeding out *our* usage, if we still need to include this jar I recommend we update to the latest release 3.0.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.