Le 01/01/2017 à 16:47, Shawn McKinney a écrit :
>> On Jan 1, 2017, at 3:47 AM, Pierre Smits wrote:
>>
>> First of all: Happy New Year. May it be an exciting and interesting one!
>>
>> It seems to me that having user guides as static pages we create the
>> impression that they are applicable to a
> On Jan 1, 2017, at 3:47 AM, Pierre Smits wrote:
>
> First of all: Happy New Year. May it be an exciting and interesting one!
>
> It seems to me that having user guides as static pages we create the
> impression that they are applicable to any version available to the
> adopters of our product
Thanks a lot, Shawn ! Great job !
Le 01/01/2017 à 10:47, Pierre Smits a écrit :
> Great work, Shawn,
>
> First of all: Happy New Year. May it be an exciting and interesting one!
>
> It seems to me that having user guides as static pages we create the
> impression that they are applicable to any
Great work, Shawn,
First of all: Happy New Year. May it be an exciting and interesting one!
It seems to me that having user guides as static pages we create the
impression that they are applicable to any version available to the
adopters of our products (old, superseded versions and the latest
av
> On Dec 18, 2016, at 11:54 AM, Emmanuel Lécharny wrote:
>
> Obviously, there is a lot of thing to add... I think the structure might
> also be improved. Anyway, we have something to start with...
>
> If you feel like to start reviewing the completed pages, please do so !
Hello,
I have comple
Le 18/12/16 à 17:56, Shawn McKinney a écrit :
>> On Dec 17, 2016, at 9:28 AM, Emmanuel Lécharny wrote:
>>
>> FTR, I ported all the Javadoc fixes to teh 'vaue' branch (which will
>> become the API 2.0 version later).
> Emmanuel,
>
> Can you provide a pointer to where these docs reside and suggest
> On Dec 17, 2016, at 9:28 AM, Emmanuel Lécharny wrote:
>
> FTR, I ported all the Javadoc fixes to teh 'vaue' branch (which will
> become the API 2.0 version later).
Emmanuel,
Can you provide a pointer to where these docs reside and suggestions on what
help is needed on them if any? Sorry, I
FTR, I ported all the Javadoc fixes to teh 'vaue' branch (which will
become the API 2.0 version later).
Le 02/12/16 à 12:53, Shawn McKinney a écrit :
>> On Dec 1, 2016, at 11:36 PM, Emmanuel Lécharny wrote:
>>
>> - SonarLint : done
>> - Javadoc : done
>>
>>
>> next (big) step : complete the site
> On Dec 1, 2016, at 11:36 PM, Emmanuel Lécharny wrote:
>
> - SonarLint : done
> - Javadoc : done
>
>
> next (big) step : complete the site documentation :-) Another two to
> three weeks, IMO...
Nice work. As stated before I can help with the site doc.
Le 26/11/16 à 13:39, Shawn McKinney a écrit :
>> On Nov 26, 2016, at 3:08 AM, Emmanuel Lécharny wrote:
>>
>> I think we are good to go for a GA soon. I'm currently cleaning up the
>> code, removing some SonarLint warnings, and adding soem missing Javadoc.
>>
> Great
- SonarLint : done
- Javadoc
FTR, here is the number of Javadoc errors that need to be fixed :
api-ldap-client-api 19
api-ldap-codec-core 190
api-ldap-extras-codec94
api-ldap-extras-codec-api74
api-ldap-extras-trigger 49
api-ldap-model 411
total 837
This
FTR, first step achieved : I have cleaned up the code, trying to remove
as much checkstyle/sonarlint errors as possible.
It may seems a waste of time, but in the process I was able to fix a few
serious mistakes that were never caught by unit tests (usage of &
instead of &&, and some potential NPE
>> On Nov 26, 2016, at 3:08 AM, Emmanuel Lécharny wrote:
>>
>> The idea is to have the cleanest possible Javadoc, and to have a
>> completed documentation on the web site, so as soon as I'm done with the
>> Javadoc, I will be completing the documention (which requires a lot of
>> love...)
>>
>> F
> On Nov 26, 2016, at 3:08 AM, Emmanuel Lécharny wrote:
>
> I think we are good to go for a GA soon. I'm currently cleaning up the
> code, removing some SonarLint warnings, and adding soem missing Javadoc.
>
Great
>
> On Nov 26, 2016, at 3:08 AM, Emmanuel Lécharny wrote:
>
> The idea is to
14 matches
Mail list logo
