You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by Emmanuel Lécharny <el...@gmail.com> on 2018/03/06 08:46:12 UTC
Current work in API
Hi guys,
Now that transaction support has been added in the API, and some
important refactoring was done in ApacheDS to make JDBM more reliable, I
have started to fix some pending issues in the LDAP API, in order to get
a release cut soon.
I'm currently fixing an issue where the Syncrepl SyncInfoValue
Intermediate response was treated as a control. The idea is to add a
third extension to the API, beside Controls and Extended operations.
That should be done this week.
I also started refactoring a bit the I18n class, using a more rational
numbering scheme. Here is what I'd like to come with - it will take a
bit of time - :
api-asn1-api: 0 - 999
api-asn1-ber: 1000 - 1999
<>: 1000 - 1099
actions: 1100 - 1199
grammar: 1200 - 1299
tlv: 1300 - 1399
api-dsml-engine 2000 - 2999
api-dsml-parser 3000 - 3999
<>: 3000 - 3099
actions: 3100 - 3199
request: 3200 - 3299
response: 3300 - 3399
api-ldap-client-api: 4000 - 4999
<>: 4000 - 4099
api: 4100 - 4199
template: 4200 - 4299
api-ldap-codec-core: 5000 - 5999
<>: 5000 - 5099
actions: 5100 - 5199
api: 5200 - 5299
controls: 5300 - 5399
osgi: 5400 - 5499
search: 5500 - 5599
api-ldap-codec-standalone: 6000 - 6999
api-ldap-extras-aci: 7000 - 7999
api-ldap-extras-codec: 8000 - 8999
<>: 8000 - 8099
controls: 8100 - 8199
extended: 8200 - 8299
intermediate: 8300 - 8399
api-ldap-extras-codec-api: 9000 - 9999
<>: 9000 - 9099
controls: 9100 - 9199
extended: 9200 - 9299
intermediate: 9300 - 9399
api-ldap-extras-sp: 10000 - 10999
api-ldap-extras-trigger: 11000 - 11999
api-ldap-extras-util: 12000 - 12999
api-ldap-model: 13000 - 13999
<>: 13000 - 13099
cursor: 13100 - 13199
entry: 13200 - 13299
filter: 13300 - 13399
ldif: 13400 - 13499
message: 13500 - 13599
name: 13600 - 13699
schema: 13700 - 13799
subtree: 13800 - 13899
api-ldap-net-mina: 14000 - 14999
api-ldap-schema-converter: 15000 - 15999
api-ldap-schema-data: 16000 - 16999
api-util: 17000 - 17999
I'm also adding text to each error (many are missing). This is not going
to break anything, it's just cosmetic. In any case, this will not be a
blocker for a release, and I may not be done this week anyway.
I will also try to fix a few other JIRAs in the mean time.
Last, not least, I'm waiting for a new release of MINA (2.0.17) which
will be cut today - so it will be available by the end of this week.
I hope to have enough time to get the release cut this week-end.
Last, not least, we have to review our packaging to get rid of MD5
signatures per the new rules. That is really a no-brainer.
Have a nice week !
--
Emmanuel Lecharny
Symas.com
directory.apache.org
Re: Done, was Re: Current work in API
Posted by Stefan Seelmann <ma...@stefan-seelmann.de>.
On 03/18/2018 05:15 PM, Emmanuel Lécharny wrote:
>
>
> Le 18/03/2018 à 14:44, Stefan Seelmann a écrit :
>> Great, many thanks Emmanuel!
>>
>> I'll look into Studio, fix the build, upgrade to Eclipse Oxygen...
>
> Lot's of work :-)
>
> As you have seen, I have added a SonarQube jenkins instance for the LDAP
> API. Seemq like some of teh OSGi tests are failing randomely...
Yes, but the other job dir-ldap-api-ubuntu-deploy works well. I have no
idea why ;)
> Otherwise, be aware that the latest version of ApacheDS brings some
> *big* change in the way we store data : we now only use one single file
> instead of one per index. That raises a question regarding those who
> will want to migrate (and that's also true for Studio).
>
> If you have any idea on how to handle that properly, I'm all ears :-)
Well, I think during the long milestone period we broke backward
compatibility multiple times, right? So either continue with that
reckless behaviour and tell user to export the data before ugprade. Or
add some migration code which is probably lot of work.
Kind Regards,
Stefan
Re: Done, was Re: Current work in API
Posted by Emmanuel Lécharny <el...@gmail.com>.
Le 18/03/2018 à 14:44, Stefan Seelmann a écrit :
> Great, many thanks Emmanuel!
>
> I'll look into Studio, fix the build, upgrade to Eclipse Oxygen...
Lot's of work :-)
As you have seen, I have added a SonarQube jenkins instance for the LDAP
API. Seemq like some of teh OSGi tests are failing randomely...
Otherwise, be aware that the latest version of ApacheDS brings some
*big* change in the way we store data : we now only use one single file
instead of one per index. That raises a question regarding those who
will want to migrate (and that's also true for Studio).
If you have any idea on how to handle that properly, I'm all ears :-)
Thanks !
--
Emmanuel Lecharny
Symas.com
directory.apache.org
Re: Done, was Re: Current work in API
Posted by Stefan Seelmann <ma...@stefan-seelmann.de>.
Great, many thanks Emmanuel!
I'll look into Studio, fix the build, upgrade to Eclipse Oxygen...
On 03/17/2018 07:14 AM, Emmanuel Lécharny wrote:
> Hi guys,
>
> I just committed the modifications I was wroking on :
> - making the SyncInfoValue a IntermediateResponse, not a control
> - started to implement teh I18n refactoring - and that includes giving
> real names instead of just a number for errors/messages
>
> As those changes impact ApacheDS, I also pushed the changes to APacheDS
> code, which now builds.
>
> As a matter of fact, I also fixed a nasty bug in LdapNetworkConnection -
> that was already fixed in trunk : there was a loop with no break making
> tests failing.
>
> We also have a MINA 2.0.17 release, I will include it.
>
> We are now close to a release of teh LDAP API and ApacheDS, I will do a
> bug parade this week-end, and also apply the few suggested pacthes.
>
> Thanks !
>
Done, was Re: Current work in API
Posted by Emmanuel Lécharny <el...@gmail.com>.
Hi guys,
I just committed the modifications I was wroking on :
- making the SyncInfoValue a IntermediateResponse, not a control
- started to implement teh I18n refactoring - and that includes giving
real names instead of just a number for errors/messages
As those changes impact ApacheDS, I also pushed the changes to APacheDS
code, which now builds.
As a matter of fact, I also fixed a nasty bug in LdapNetworkConnection -
that was already fixed in trunk : there was a loop with no break making
tests failing.
We also have a MINA 2.0.17 release, I will include it.
We are now close to a release of teh LDAP API and ApacheDS, I will do a
bug parade this week-end, and also apply the few suggested pacthes.
Thanks !
Le 06/03/2018 à 09:46, Emmanuel Lécharny a écrit :
> Hi guys,
>
> Now that transaction support has been added in the API, and some
> important refactoring was done in ApacheDS to make JDBM more reliable, I
> have started to fix some pending issues in the LDAP API, in order to get
> a release cut soon.
>
> I'm currently fixing an issue where the Syncrepl SyncInfoValue
> Intermediate response was treated as a control. The idea is to add a
> third extension to the API, beside Controls and Extended operations.
> That should be done this week.
>
> I also started refactoring a bit the I18n class, using a more rational
> numbering scheme. Here is what I'd like to come with - it will take a
> bit of time - :
>
> api-asn1-api: 0 - 999
>
> api-asn1-ber: 1000 - 1999
> <>: 1000 - 1099
> actions: 1100 - 1199
> grammar: 1200 - 1299
> tlv: 1300 - 1399
>
> api-dsml-engine 2000 - 2999
>
> api-dsml-parser 3000 - 3999
> <>: 3000 - 3099
> actions: 3100 - 3199
> request: 3200 - 3299
> response: 3300 - 3399
>
> api-ldap-client-api: 4000 - 4999
> <>: 4000 - 4099
> api: 4100 - 4199
> template: 4200 - 4299
>
> api-ldap-codec-core: 5000 - 5999
> <>: 5000 - 5099
> actions: 5100 - 5199
> api: 5200 - 5299
> controls: 5300 - 5399
> osgi: 5400 - 5499
> search: 5500 - 5599
>
> api-ldap-codec-standalone: 6000 - 6999
>
> api-ldap-extras-aci: 7000 - 7999
>
> api-ldap-extras-codec: 8000 - 8999
> <>: 8000 - 8099
> controls: 8100 - 8199
> extended: 8200 - 8299
> intermediate: 8300 - 8399
>
> api-ldap-extras-codec-api: 9000 - 9999
> <>: 9000 - 9099
> controls: 9100 - 9199
> extended: 9200 - 9299
> intermediate: 9300 - 9399
>
> api-ldap-extras-sp: 10000 - 10999
>
> api-ldap-extras-trigger: 11000 - 11999
>
> api-ldap-extras-util: 12000 - 12999
>
> api-ldap-model: 13000 - 13999
> <>: 13000 - 13099
> cursor: 13100 - 13199
> entry: 13200 - 13299
> filter: 13300 - 13399
> ldif: 13400 - 13499
> message: 13500 - 13599
> name: 13600 - 13699
> schema: 13700 - 13799
> subtree: 13800 - 13899
>
> api-ldap-net-mina: 14000 - 14999
>
> api-ldap-schema-converter: 15000 - 15999
>
> api-ldap-schema-data: 16000 - 16999
>
> api-util: 17000 - 17999
>
>
> I'm also adding text to each error (many are missing). This is not going
> to break anything, it's just cosmetic. In any case, this will not be a
> blocker for a release, and I may not be done this week anyway.
>
> I will also try to fix a few other JIRAs in the mean time.
>
> Last, not least, I'm waiting for a new release of MINA (2.0.17) which
> will be cut today - so it will be available by the end of this week.
>
> I hope to have enough time to get the release cut this week-end.
>
> Last, not least, we have to review our packaging to get rid of MD5
> signatures per the new rules. That is really a no-brainer.
>
> Have a nice week !
>
--
Emmanuel Lecharny
Symas.com
directory.apache.org