Hi guys,
I've been a bit silent those last days, being stuck with loads of work
and parenting tasks...
I will try to get the site updated tonite (EU time) with SCIMple on it.
I will do that on the staging site, so you can provide some feedback
before we publish the site to the world. We may nee
Hi guys,
a quick update :
SCIMple :
-
- the SCIMple basic we site is done
(http://directory.staging.apache.org/scimple)
- the SCIMple JIRA space has been created
(https://issues.apache.org/jira/projects/SCIMPLE), an I have made Shawn
Smith admin of this space
ApacheDS :
--
- I
Thanks Emmanuel!
On 07/02/2018 03:30 PM, Emmanuel Lécharny wrote:
> ApacheDS :
> --
>
> - I have fixed the failing startTLS test (which was in fact an LDAP API
> error : the SslFilter was not added to the chain)
> - ApacheDS is now building fine
>
> I think I will start to cut a release
On 07/02/2018 07:58 PM, Stefan Seelmann wrote:
> Thanks Emmanuel!
>
> On 07/02/2018 03:30 PM, Emmanuel Lécharny wrote:
>> ApacheDS :
>> --
>>
>> - I have fixed the failing startTLS test (which was in fact an LDAP API
>> error : the SslFilter was not added to the chain)
>> - ApacheDS is now
moved, or are there other intermediate steps we should take?
Shawn
From: Stefan Seelmann
Sent: Tuesday, July 3, 2018 4:35:53 PM
To: dev@directory.apache.org
Subject: Re: SCIMple, current state of Apache LDAP 2.0, and Java 9/10/11
On 07/02/2018 07:58 PM, Stefan
Le 03/07/2018 à 22:52, Smith, Shawn E a écrit :
> Thanks Emmanuel. I've started closing old completed issues in the current
> repository and will migrate those that are left. We should be able to get
> the code moved over in the next day or two as well.
>
>
> Would it be preferable to put
Le 03/07/2018 à 22:35, Stefan Seelmann a écrit :
> On 07/02/2018 07:58 PM, Stefan Seelmann wrote:
>> Thanks Emmanuel!
>>
>> On 07/02/2018 03:30 PM, Emmanuel Lécharny wrote:
>>> ApacheDS :
>>> --
>>>
>>> - I have fixed the failing startTLS test (which was in fact an LDAP API
>>> error : th
Hi,
On 07/01/2018 09:40 AM, Emmanuel Lécharny wrote:
Otherwise, the APache LDAP API 2.0 is on its way, I have fixed a long
lasting ticket about reshuffling the error/messages numbering - quite a
pain in the back...- and I still have a pending issue in ApacheDS with
this revision : one failing te
Le 09/07/2018 à 13:46, Radovan Semancik a écrit :
> Hi,
>
> On 07/01/2018 09:40 AM, Emmanuel Lécharny wrote:
>> Otherwise, the APache LDAP API 2.0 is on its way, I have fixed a long
>> lasting ticket about reshuffling the error/messages numbering - quite a
>> pain in the back...- and I still hav
On 07/09/2018 02:54 PM, Emmanuel Lécharny wrote:
I guess most of the errors are produced by the
DefaultSchemaObjectRegistry class.
If so, I wonder if a more simple solution would'nt be to create a
specific Logger for such a thing as AD, and configure the property file
to mute the other loggers.
Le 09/07/2018 à 15:28, Radovan Semancik a écrit :
>> One last solution : pass a flag (like 'MUTE_WARNINGS') to the API while
>> processing a schema, and have something like :
>>
>> if ( LOG.isWarnEnabled() && !muteWarnings )
>> {
>> LOG.warn( msg );
>>
11 matches
Mail list logo