[GitHub] commons-imaging issue #27: Increase code coverage one

[TheRealHaui]

Github user TheRealHaui commented on the issue:

https://github.com/apache/commons-imaging/pull/27
  
@garydgregory 
Thanks for your response.
Looked over the secretary@ section ...

Referring to your question if some of the tests were generated:
I use a lot of tools on top of my IDE that advise and suggest me where and 
how to improve code.
Some - like the Sonar plugin give advice concerning code improvements.
Some like code coverage tools advice me which lines/branches of code are 
not covered through automated tests yet.
And to those I sticked in the end here.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

[GitHub] commons-imaging issue #27: Increase code coverage one

[garydgregory]

Github user garydgregory commented on the issue:

https://github.com/apache/commons-imaging/pull/27
  
Please see https://www.apache.org/licenses/#submitting



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

[GitHub] commons-imaging issue #27: Increase code coverage one

[TheRealHaui]

Github user TheRealHaui commented on the issue:

https://github.com/apache/commons-imaging/pull/27
  
@garydgregory 
You're welcome.
Where to send the pdf to?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [dbutils] Preparing for Release; Questions

[Carl Hall]

Maven setup!  I dug through the pom parent chain to get the right server id
(apache.releases.https) and get my creds setup correctly.  I was able to
complete the deploy step, and am now working through the final steps.

Regarding syncing, nothing has changed.  I think Benedikt may be right
about filing a ticket.

On Tue, Jul 11, 2017 at 12:45 PM, Gary Gregory 
wrote:

> Are they in sync now? Make sure you have you Maven settings set up just so.
> I think Maven has some docs on how to encrypted and save your passwords.
>
> Gary
>
> On Mon, Jul 10, 2017 at 8:57 PM, Carl Hall  wrote:
>
> > Hey Gary,
> >
> > Thanks for adding me, but I'm getting the same error message as before.
> I
> > checked my profile in whimsy and I appear to be a committer on commons
> and
> > part of the "committers" group.
> > It might be completely unrelated, but Github and git.a.o aren't in sync
> > with git-wip-us.a.o.  Maybe some weirdo setup thing somewhere?
> >
> > On Sun, Jul 9, 2017 at 2:48 PM, Gary Gregory 
> > wrote:
> >
> > > Hi Carl,
> > >
> > > As you already are an Apache Committer, I've added you to the Commons
> > > Committers group, please try again in a few minutes.
> > >
> > > Gary
> > >
> > > On Sun, Jul 9, 2017 at 2:08 PM, Carl Hall  wrote:
> > >
> > > > Hi all,
> > > >
> > > > I'd like to make a release of dbutils.  I've worked through the
> release
> > > > preparation guide[1] up to deploying the RC.  Rather expectedly,
> since
> > > this
> > > > is my first attempt at releasing, I'm not able to complete the `mvn
> > > deploy`
> > > > step.
> > > >
> > > > ```
> > > > Failed to transfer file:
> > > > https://repository.apache.org/service/local/staging/deploy/
> > > > maven2/commons-dbutils/commons-dbutils/1.7/commons-dbutils-1.7.jar.
> > > > Return code is: 401, ReasonPhrase: Unauthorized.
> > > > ```
> > > >
> > > > Should I ask for write permission or should I ask someone else to
> > manage
> > > > the release?
> > > >
> > > > Thanks,
> > > > Carl
> > > >
> > > > 1 https://commons.apache.org/releases/prepare.html
> > > >
> > >
> >
>

[GitHub] commons-imaging issue #27: Increase code coverage one

[garydgregory]

Github user garydgregory commented on the issue:

https://github.com/apache/commons-imaging/pull/27
  
@TheRealHaui:

Thank you for your PR. 

This is a lot of code, I think it would be appropriate for you to file a 
ICLA with us. Please see  https://www.apache.org/licenses/#clas and 
https://www.apache.org/licenses/icla.pdf

Thank you,
Gary


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [daemon] moving to git ? and bump java version.

[Gary Gregory]

It seems OK to me to update to Java 6 for now and get this to compile under
java 9 for those folks who will try...

Gary

On Wed, Jul 12, 2017 at 9:09 AM, Amey Jadiye  wrote:

> Thanks for great insights Mark.
>
> On Wed, Jul 12, 2017, 9:28 PM Mark Thomas  wrote:
>
> > On 12 July 2017 16:33:01 CEST, Matt Sicker  wrote:
> > >Are there plans to require 1.7 for Tomcat anytime? Otherwise, it might
> > >be
> > >necessary to make a new major version of daemon eventually for Java 8
> > >or 9.
> >
> > Tomcat major versions are aligned with Java EE versions which in turn
> have
> > a minimum Java version.
> >
> > Tomcat supports 3 current versions in parallel so we currently have:
> >
> > Tomcat 9 - Java EE 8 - Java 8
> > Tomcat 8 - Java EE 7 - Java 7
> > Tomcat 7 - Java EE 6 - Java 6
> >
> > Tomcat 7 support will continue until at least Java EE 9 is released. That
> > is meant to be next year but there are no firm dates yet and experience
> > suggests the Java EE 9 release date will slip.
> >
> > On that basis I expect Tomcat to need a Daemon that supports Java 6 for
> at
> > least 2 more years.
> >
> > Is there a user requirement driving an increase in the minimum Java
> > version? If not, I suggest we stick with 6 for now.
> >
>
> There is no user requirement , Commons daemon is still keeping minimum
> dependency on java 1.5, we were thinking to move on minimum 1.6, nice to
> hear there won't be any issue with tomcat since it's already on 1.6
>
> For moving to much higher i.e. java 1.7 I'm sure daemon will take another
> 2-3 year for keeping stability across projects.
>
> Regards,
> Amey
>
> Mark
> >
> >
> > >
> > >Anyways, 1.6 minimum makes sense to me mainly due to Java 9's compiler
> > >not
> > >supporting Java 5 targets anymore.
> > >
> > >On 12 July 2017 at 09:19, Mark Thomas  wrote:
> > >
> > >> On 11 July 2017 21:02:54 CEST, Amey Jadiye 
> > >wrote:
> > >> >Hi Daemon Maintainers / All,
> > >> >
> > >> >Daemon seems to be still being maintained on svn, do we have any
> > >plan
> > >> >moving code base to git ?
> > >>
> > >> No preference on this.
> > >>
> > >> >As fact there is low activity in daemon no one thought of bumping
> > >> >version
> > >> >from 1.5 to 1.6 OR we are keeping it purposefully to 1.5 ?
> > >> >shall we bump it minimum to 1.6 ?
> > >>
> > >> 1.6 is OK for Tomcat. Anything higher will cause problems.
> > >>
> > >> Mark
> > >>
> > >> -
> > >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> > >> For additional commands, e-mail: dev-h...@commons.apache.org
> > >>
> > >>
> >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> > For additional commands, e-mail: dev-h...@commons.apache.org
> >
> >
>

[GitHub] commons-imaging issue #27: Increase code coverage one

[garydgregory]

Github user garydgregory commented on the issue:

https://github.com/apache/commons-imaging/pull/27
  
Where some of these generated?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

[GitHub] commons-text issue #49: TEXT-89: WordUtils.initials support for UTF-16 surro...

[arunvinudss]

Github user arunvinudss commented on the issue:

https://github.com/apache/commons-text/pull/49
  
@ameyjadiye Done.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

[GitHub] commons-text issue #49: TEXT-89: WordUtils.initials support for UTF-16 surro...

[coveralls]

Github user coveralls commented on the issue:

https://github.com/apache/commons-text/pull/49
  

[![Coverage 
Status](https://coveralls.io/builds/12387036/badge)](https://coveralls.io/builds/12387036)

Coverage decreased (-0.2%) to 97.126% when pulling 
**15c2e4b28686edf6f0807304367dba82ac3d359d on arunvinudss:TEXT-89** into 
**aaf4aba369ed0b97d17bc9343f763b0d099dbc2f on apache:master**.



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

[GitHub] commons-imaging pull request #27: Increase code coverage one

[TheRealHaui]

GitHub user TheRealHaui opened a pull request:

https://github.com/apache/commons-imaging/pull/27

Increase code coverage one

I have created Unit Tests to increase code coverage which I want to 
contribute.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/TheRealHaui/commons-imaging 
increase-code-coverage-one

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/commons-imaging/pull/27.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #27


commit 127469460ab0ae0d12d35b4e0b5056af6debdea2
Author: Michael Hausegger 
Date:   2017-07-13T20:12:46Z

increase-code-coverage-one Added Unit Tests to increase code coverage.

commit 8e48087803a12106f1d8b88803a94557f031ec62
Author: Michael Hausegger 
Date:   2017-07-13T21:00:31Z

increase-code-coverage-one Added Unit Tests to increase code coverage.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

RE: [lang] - Remove RandomStringUtils deprecation / move it to [text]?

[dbrosIus]

I just ran into this the other day. Was going to switch to the commons-text 
version, but it was to much trouble and decided to stick with the deprecated 
version in Commons-lang 

 Original message 
From: Pascal Schumacher  
Date: 7/13/17  4:02 PM  (GMT-05:00) 
To: Commons Developers List  
Subject: [lang] - Remove RandomStringUtils deprecation / move it to [text]? 

Hello everybody,

with 3.5 we deprecated RandomStringUtils in favor of 
RandomStringGenerator in commons-text.

https://issues.apache.org/jira/browse/TEXT-96 complains that 
"RandomStringGenerator is extremely verbose compared to the deprecated 
commons.lang3 RandomStringUtils."

 From my experience taking a look at migrating a project from 
RandomStringUtils to RandomStringGenerator I have to agree. Some 
convenience methods will be added with the next commons text release, 
but it still won't be as easy to use as RandomStringUtils. For course 
RandomStringGenerator gives the user more options, but most usage of 
RandomStringUtils I have seen was just for tests or other simple 
use-cases where these option are not required.

Maybe we should just remove the RandomStringUtils deprecation or add the 
whole class untouched to commons-text?

What do you think?

Cheers,

Pascal

Re: [lang] - Remove RandomStringUtils deprecation / move it to [text]?

[Gary Gregory]

Can one be pitch for entry level and the other for advanced use cases?

If so, just un-deprecate but still Javadoc to [text] the user's edification.

Gary

On Thu, Jul 13, 2017 at 1:02 PM, Pascal Schumacher  wrote:

> Hello everybody,
>
> with 3.5 we deprecated RandomStringUtils in favor of RandomStringGenerator
> in commons-text.
>
> https://issues.apache.org/jira/browse/TEXT-96 complains that
> "RandomStringGenerator is extremely verbose compared to the deprecated
> commons.lang3 RandomStringUtils."
>
> From my experience taking a look at migrating a project from
> RandomStringUtils to RandomStringGenerator I have to agree. Some
> convenience methods will be added with the next commons text release, but
> it still won't be as easy to use as RandomStringUtils. For course
> RandomStringGenerator gives the user more options, but most usage of
> RandomStringUtils I have seen was just for tests or other simple use-cases
> where these option are not required.
>
> Maybe we should just remove the RandomStringUtils deprecation or add the
> whole class untouched to commons-text?
>
> What do you think?
>
> Cheers,
>
> Pascal
>
>

[lang] - Remove RandomStringUtils deprecation / move it to [text]?

[Pascal Schumacher]

Hello everybody,

with 3.5 we deprecated RandomStringUtils in favor of 
RandomStringGenerator in commons-text.


https://issues.apache.org/jira/browse/TEXT-96 complains that 
"RandomStringGenerator is extremely verbose compared to the deprecated 
commons.lang3 RandomStringUtils."


From my experience taking a look at migrating a project from 
RandomStringUtils to RandomStringGenerator I have to agree. Some 
convenience methods will be added with the next commons text release, 
but it still won't be as easy to use as RandomStringUtils. For course 
RandomStringGenerator gives the user more options, but most usage of 
RandomStringUtils I have seen was just for tests or other simple 
use-cases where these option are not required.


Maybe we should just remove the RandomStringUtils deprecation or add the 
whole class untouched to commons-text?


What do you think?

Cheers,

Pascal

Re: [daemon] : fixing some general stuff

[Gary Gregory]

Reviewed.

Gary

On Thu, Jul 13, 2017 at 12:01 PM, Amey Jadiye  wrote:

> If maintainers are not around, can someone please review this ?
>
> Regards,
> Amey
>
> On Tue, Jul 11, 2017 at 11:51 PM, Amey Jadiye 
> wrote:
>
> > Hi All,
> >
> > Its was quite tedious task but I have fixed almost all errors from the
> > commons daemon from maven perspective and below default goals running
> > clean, I would appreciate if someone take look at PR.
> > https://github.com/apache/commons-daemon/pull/3
> >
> > mvn clean verify apache-rat:check clirr:check checkstyle:check
> > findbugs:check javadoc:javadoc
> >
> > checkstyle:check  :-  178 Errors, corrected all of them.
> > javadoc:javadoc   :-   20+ Error, corrected all of them.
> > apache-rat:check :-  4 Errors, placed file in rat exclusion.
> > findbugs:check :-  4 Errors, corrected all.
> > clirr:check :-  This was running good.
> >
> >
> > for the junit test cases additions will open another jira to track.
> >
> > Regards,
> > Amey
> >
> >
> >
> >
> > On Mon, Jul 10, 2017 at 12:34 AM, Amey Jadiye 
> > wrote:
> >
> >> Hi Bernd/Mark/All,
> >>
> >> I have raised PR to cover this, would you mind just take a look ?
> >> https://github.com/apache/commons-daemon/pull/3
> >> So far I have fixed rat, findbug. I will push javadoc and checkstyle
> >> sometime tomorrow.
> >>
> >> Regards,
> >> Amey
> >>
> >> On Sun, Jul 9, 2017 at 9:34 PM, Amey Jadiye 
> wrote:
> >>
> >>> Thanks Bernd,
> >>>
> >>> I had plan B for those crying rat, will put those files to exclusion of
> >>> checking.
> >>>
> >>> I can take care of checkstyle, findbug, javadoc.
> >>>
> >>> I'm more interested about test cases now. do we have any options around
> >>> C code coverage with maven [ java code coverage is easy though], OR
> even is
> >>> that required?
> >>>
> >>> Regards,
> >>> Amey
> >>>
> >>>
> >>> On Sun, Jul 9, 2017, 9:26 PM Bernd Eckenfels 
> >>> wrote:
> >>>
>  Hello,
> 
>  I think the autoconf related files are generated by GNU tools and
>  cannot be re-licensed. They are not in the binary packages but they do
>  contaminate the source archives. It is not yet mentioned in the
> NOTICE file
>  but I guess there is a ASF wide regulation for those build scripts.
> Does
>  anybody know?
> 
>  Thanks for looking at the issues, would be good if you commit smaller
>  batches more often, since there is generally some more interest in the
>  project currently. If you want I can help with the Javadoc warnings?
> 
>  Gruss
>  Bernd
>  --
>  http://bernd.eckenfels.net
>  
>  From: Amey Jadiye 
>  Sent: Sunday, July 9, 2017 4:00:08 PM
>  To: Commons Developers List
>  Subject: [daemon] : fixing some general stuff
> 
>  Hi All,
> 
>  I'm going through apache daemon code and trying to fix the stuff
>  breaking
>  with below maven options, also would like to know if some more checks
>  can
>  be added since this repo contains lot of C code.
> 
>  mvn clean verify apache-rat:check clirr:check checkstyle:check
>  findbugs:check javadoc:javadoc
> 
>  couple of things I'd like to discuss and get opinion.
> 
>  #1. TESTS: No test cases present, adding some could be a good add [at
>  least
>  for java code], not idea about C code.
> 
>  #2. RAT : apache-rat is crying for  4 files, it is ok to add APACHE
>  LICENSE
>  but I found they already have GPLv3 in them, shall we replace them, or
>  we
>  need consent ?
>  src/native/unix/support/config.sub
>  src/native/unix/support/config.guess
>  src/native/unix/native/.indent.pro
> 
>  #3. CLIRR : building good.
> 
>  #4. CHECKSTYLE: Hell lot of mess, 170+ errors, but I can take them
> down
>  one
>  by one, no big deal.
> 
>  #5   FINDBUG: 4 bugs, no big deal.
> 
>  #6. JAVADOC: Few bugs, again no big deal.
> 
>  Regards,
>  Amey
> 
>  -
>  To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>  For additional commands, e-mail: dev-h...@commons.apache.org
> 
> >>>
> >>
> >>
> >> --
> >>
> >> -
> >>
> >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> >>
> >> For additional commands, e-mail: dev-h...@commons.apache.org
> >>
> >
> >
> >
> > --
> >
> > -
> >
> > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> >
> > For additional commands, e-mail: dev-h...@commons.apache.org
> >
>
>
>
> --
>
> -
>
> To unsubscribe, e-mail: 

Re: [daemon] : fixing some general stuff

[Amey Jadiye]

If maintainers are not around, can someone please review this ?

Regards,
Amey

On Tue, Jul 11, 2017 at 11:51 PM, Amey Jadiye  wrote:

> Hi All,
>
> Its was quite tedious task but I have fixed almost all errors from the
> commons daemon from maven perspective and below default goals running
> clean, I would appreciate if someone take look at PR.
> https://github.com/apache/commons-daemon/pull/3
>
> mvn clean verify apache-rat:check clirr:check checkstyle:check
> findbugs:check javadoc:javadoc
>
> checkstyle:check  :-  178 Errors, corrected all of them.
> javadoc:javadoc   :-   20+ Error, corrected all of them.
> apache-rat:check :-  4 Errors, placed file in rat exclusion.
> findbugs:check :-  4 Errors, corrected all.
> clirr:check :-  This was running good.
>
>
> for the junit test cases additions will open another jira to track.
>
> Regards,
> Amey
>
>
>
>
> On Mon, Jul 10, 2017 at 12:34 AM, Amey Jadiye 
> wrote:
>
>> Hi Bernd/Mark/All,
>>
>> I have raised PR to cover this, would you mind just take a look ?
>> https://github.com/apache/commons-daemon/pull/3
>> So far I have fixed rat, findbug. I will push javadoc and checkstyle
>> sometime tomorrow.
>>
>> Regards,
>> Amey
>>
>> On Sun, Jul 9, 2017 at 9:34 PM, Amey Jadiye  wrote:
>>
>>> Thanks Bernd,
>>>
>>> I had plan B for those crying rat, will put those files to exclusion of
>>> checking.
>>>
>>> I can take care of checkstyle, findbug, javadoc.
>>>
>>> I'm more interested about test cases now. do we have any options around
>>> C code coverage with maven [ java code coverage is easy though], OR even is
>>> that required?
>>>
>>> Regards,
>>> Amey
>>>
>>>
>>> On Sun, Jul 9, 2017, 9:26 PM Bernd Eckenfels 
>>> wrote:
>>>
 Hello,

 I think the autoconf related files are generated by GNU tools and
 cannot be re-licensed. They are not in the binary packages but they do
 contaminate the source archives. It is not yet mentioned in the NOTICE file
 but I guess there is a ASF wide regulation for those build scripts. Does
 anybody know?

 Thanks for looking at the issues, would be good if you commit smaller
 batches more often, since there is generally some more interest in the
 project currently. If you want I can help with the Javadoc warnings?

 Gruss
 Bernd
 --
 http://bernd.eckenfels.net
 
 From: Amey Jadiye 
 Sent: Sunday, July 9, 2017 4:00:08 PM
 To: Commons Developers List
 Subject: [daemon] : fixing some general stuff

 Hi All,

 I'm going through apache daemon code and trying to fix the stuff
 breaking
 with below maven options, also would like to know if some more checks
 can
 be added since this repo contains lot of C code.

 mvn clean verify apache-rat:check clirr:check checkstyle:check
 findbugs:check javadoc:javadoc

 couple of things I'd like to discuss and get opinion.

 #1. TESTS: No test cases present, adding some could be a good add [at
 least
 for java code], not idea about C code.

 #2. RAT : apache-rat is crying for  4 files, it is ok to add APACHE
 LICENSE
 but I found they already have GPLv3 in them, shall we replace them, or
 we
 need consent ?
 src/native/unix/support/config.sub
 src/native/unix/support/config.guess
 src/native/unix/native/.indent.pro

 #3. CLIRR : building good.

 #4. CHECKSTYLE: Hell lot of mess, 170+ errors, but I can take them down
 one
 by one, no big deal.

 #5   FINDBUG: 4 bugs, no big deal.

 #6. JAVADOC: Few bugs, again no big deal.

 Regards,
 Amey

 -
 To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
 For additional commands, e-mail: dev-h...@commons.apache.org

>>>
>>
>>
>> --
>>
>> -
>>
>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>>
>> For additional commands, e-mail: dev-h...@commons.apache.org
>>
>
>
>
> --
>
> -
>
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>
> For additional commands, e-mail: dev-h...@commons.apache.org
>



-- 

-

To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org

For additional commands, e-mail: dev-h...@commons.apache.org