[Fortress] Git import and JIRA migration on their way
Hi guys, I have requested teh import of the current Git repo and the migration of the existing JIRA : https://issues.apache.org/jira/browse/INFRA-8470 and https://issues.apache.org/jira/browse/INFRA-8483 It might take a few days. Thanks !
Re: Fortress IP clearance
On 10/15/2014 01:34 AM, Emmanuel Lécharny wrote: > At this point, and focusing on Fortress-core only, I wouls suggest we > simply get rid of Uboundid dependency, and then we should be good to go. > > Anyone has another take on this matter ? Seems reasonable, though as previously stated there will be a bit of work to complete the DAO integration with apache ldap API (password policy + a couple of utility entities - suffix and container) to pass all of the junit tests. The realm package is just fortress + a tomcat lib so might be worth doing at same time as core.
[jira] [Commented] (DIRSERVER-265) In-memory backend storage support
[ https://issues.apache.org/jira/browse/DIRSERVER-265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14172269#comment-14172269 ] Josef Cacek commented on DIRSERVER-265: --- I made a blog post about the "in-memory LDAP" solution which we use in the WildFly testsuite now: http://javlog.cacek.cz/2014/09/speed-up-apacheds-ldap-server.html > In-memory backend storage support > - > > Key: DIRSERVER-265 > URL: https://issues.apache.org/jira/browse/DIRSERVER-265 > Project: Directory ApacheDS > Issue Type: New Feature > Components: core >Affects Versions: 1.0-RC1 >Reporter: Trustin Lee > Fix For: 2.0.0-M16 > > > Users that use ApacheDS as an embedded JNDI provider might want to use > in-memory backend storage which will show very fast startup time and > performance. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
