Re: [configuration] Java 8 types

[Jochen Wiedmann]

+1


On Wed, Mar 28, 2018 at 9:06 PM, Gary Gregory  wrote:
> Hi All:
>
> I say it is time to update Commons Configuration to Java 8 and support the
> types in java.time.
>
> Thoughts?
>
> Gary

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

[configuration] Java 8 types

[Gary Gregory]

Hi All:

I say it is time to update Commons Configuration to Java 8 and support the
types in java.time.

Thoughts?

Gary

Re: [DISCUSS] new component for timing?

[Otto Fowler]

OK, sounds fine to me.  Hopefully we’ll get some buy in and can move
forward.
I’m not sure what is next though ;)



On March 28, 2018 at 13:17:22, Gary Gregory (garydgreg...@gmail.com) wrote:

On Wed, Mar 28, 2018 at 11:14 AM, Otto Fowler 
wrote:

> How about commons-timing, having StopWatch, StackWatch and other classes
> that
> we can find?
>

I think we start small with only what we need and have today, namely these
two classes.

Gary


>
>
>
> On March 20, 2018 at 18:40:05, Romain Manni-Bucau (rmannibu...@gmail.com)
> wrote:
>
> I would be happy to revive sirona @asf but dont think [monitoring] as
just
> a few classes would bring enough value compare to a lambda not worthing
any
> lib/dep in apps - just my opinion indeed.
>
> For circuit breaker: geronimo safeguard can be interested in hosting that
> utility part and drop failsafe dependency. Maybe something to discuss in
> another thread.
>
> Le 20 mars 2018 23:27, "Otto Fowler"  a écrit :
>
> > Sirona is gone, it is a closed incubator project. Romain has forked it
to
> > his own repo.
> >
> >
> >
> > On March 20, 2018 at 18:24:06, Gilles (gil...@harfang.homelinux.org)
> > wrote:
> >
> > On Tue, 20 Mar 2018 15:00:41 -0700, Otto Fowler wrote:
> > > If monitoring was started a new, and not re-viving the old
> > > monitoring?
> >
> > Can the feature be contributed to "Sirona"? Otto, are you
> > interested in this?
> > Does it make sense to have "Commons Monitoring" revived based
> > on part/all of "Sirona"?
> > Romain, are you interested in this?
> > What would be the scope/description of "Commons Monitoring"?
> >
> > Noting Romain's experience that the original "Commons" project
> > evolved into "Sirona", it would be strange to start from scratch
> > without a plan to not follow the same route again...
> >
> > Gilles
> >
> > > On March 20, 2018 at 17:56:44, Bruno P. Kinoshita (
> > > brunodepau...@yahoo.com.br.invalid) wrote:
> > >
> > > I think StopWatch and CircuitBreakers could be moved together to the
> > > same
> > > component. However, a circuit breaker can be time-related, or not
> > > (e.g. a
> > > circuit breaker for memory size). So probably commons-timing could be
> > > a
> > > good place for StopWatch, but maybe not for circuit-breaker. But I
> > > think
> > > both could be under commons-monitoring perhaps?
> > >
> > > From: Otto Fowler 
> > > To: Romain Manni-Bucau ; Commons Developers
> > > List <
> > > dev@commons.apache.org>
> > > Sent: Wednesday, 21 March 2018 10:30 AM
> > > Subject: Re: [DISCUSS] new component for timing?
> > >
> > > I would love to get this on track. I apologize if I have made it
> > > more
> > > confusing than it needs to be,
> > > I’m trying to be open to all the suggestions.
> > >
> > > If we assume that stack watch is worth ‘having’, then the question is
> > > where
> > > to put it.
> > > commons-monitoring / sirota seems to me to be a ‘complete’ solution
> > > as
> > > opposed to
> > > a set of or collection of like classes.
> > >
> > > Setting the community support / project aspect of sirota aside, it
> > > seems
> > > strange to put
> > > a separate class into a more complete and uniform system. Unless
> > > there is
> > > some generically
> > > useful set of timing utility classes that could be taken out of
> > > sirota to
> > > go into commons-,
> > > along with things identified ( StopWatch?) out of commons lang and
> > > possibly
> > > other commons projects.
> > >
> > > commons-timing seems reasonable. Thoughts?
> > >
> > >
> > >
> > > On March 17, 2018 at 11:24:32, Romain Manni-Bucau
> > > (rmannibu...@gmail.com)
> > > wrote:
> > >
> > > Yes but consequence was a lack of community increase which is a
> > > killer for
> > > an incubator project on the long run.
> > >
> > > Le 17 mars 2018 15:19, "Gilles"  a
> > > écrit :
> > >
> > >> On Sat, 17 Mar 2018 12:47:40 +0100, Romain Manni-Bucau wrote:
> > >>
> > >>> Le 17 mars 2018 11:49, "Gilles"  a
> > >>> écrit :
> > >>>
> > >>> On Thu, 15 Mar 2018 15:13:39 +0100, Romain Manni-Bucau wrote:
> > >>>
> > >>> 2018-03-15 14:36 GMT+01:00 Otto Fowler :
> > 
> >  If we can come to consensus on the way forward, I’ll be happy to
> >  do the
> > 
> > > work ( although I’ll need help of course ).
> > > I guess I’m the straw that broke the camel’s back then? ;)
> > >
> > >
> > >
> > >
> > > On March 15, 2018 at 08:09:45, Gilles
> > > (gil...@harfang.homelinux.org)
> > > wrote:
> > >
> > > Hi.
> > >
> > > On Thu, 15 Mar 2018 03:52:58 -0700, Otto Fowler wrote:
> > > > I think bringing back commons-monitoring/sirota would only be
> > > > possible if
> > > > it were to be modular enough that you could bring in the ‘core’
> > > > classes
> > > > without needing to bring in all of what sirota ended up 

Re: [DISCUSS] new component for timing?

[Gary Gregory]

On Wed, Mar 28, 2018 at 11:14 AM, Otto Fowler 
wrote:

> How about commons-timing, having StopWatch, StackWatch and other classes
> that
> we can find?
>

I think we start small with only what we need and have today, namely these
two classes.

Gary


>
>
>
> On March 20, 2018 at 18:40:05, Romain Manni-Bucau (rmannibu...@gmail.com)
> wrote:
>
> I would be happy to revive sirona @asf but dont think [monitoring] as just
> a few classes would bring enough value compare to a lambda not worthing any
> lib/dep in apps - just my opinion indeed.
>
> For circuit breaker: geronimo safeguard can be interested in hosting that
> utility part and drop failsafe dependency. Maybe something to discuss in
> another thread.
>
> Le 20 mars 2018 23:27, "Otto Fowler"  a écrit :
>
> > Sirona is gone, it is a closed incubator project. Romain has forked it to
> > his own repo.
> >
> >
> >
> > On March 20, 2018 at 18:24:06, Gilles (gil...@harfang.homelinux.org)
> > wrote:
> >
> > On Tue, 20 Mar 2018 15:00:41 -0700, Otto Fowler wrote:
> > > If monitoring was started a new, and not re-viving the old
> > > monitoring?
> >
> > Can the feature be contributed to "Sirona"? Otto, are you
> > interested in this?
> > Does it make sense to have "Commons Monitoring" revived based
> > on part/all of "Sirona"?
> > Romain, are you interested in this?
> > What would be the scope/description of "Commons Monitoring"?
> >
> > Noting Romain's experience that the original "Commons" project
> > evolved into "Sirona", it would be strange to start from scratch
> > without a plan to not follow the same route again...
> >
> > Gilles
> >
> > > On March 20, 2018 at 17:56:44, Bruno P. Kinoshita (
> > > brunodepau...@yahoo.com.br.invalid) wrote:
> > >
> > > I think StopWatch and CircuitBreakers could be moved together to the
> > > same
> > > component. However, a circuit breaker can be time-related, or not
> > > (e.g. a
> > > circuit breaker for memory size). So probably commons-timing could be
> > > a
> > > good place for StopWatch, but maybe not for circuit-breaker. But I
> > > think
> > > both could be under commons-monitoring perhaps?
> > >
> > > From: Otto Fowler 
> > > To: Romain Manni-Bucau ; Commons Developers
> > > List <
> > > dev@commons.apache.org>
> > > Sent: Wednesday, 21 March 2018 10:30 AM
> > > Subject: Re: [DISCUSS] new component for timing?
> > >
> > > I would love to get this on track. I apologize if I have made it
> > > more
> > > confusing than it needs to be,
> > > I’m trying to be open to all the suggestions.
> > >
> > > If we assume that stack watch is worth ‘having’, then the question is
> > > where
> > > to put it.
> > > commons-monitoring / sirota seems to me to be a ‘complete’ solution
> > > as
> > > opposed to
> > > a set of or collection of like classes.
> > >
> > > Setting the community support / project aspect of sirota aside, it
> > > seems
> > > strange to put
> > > a separate class into a more complete and uniform system. Unless
> > > there is
> > > some generically
> > > useful set of timing utility classes that could be taken out of
> > > sirota to
> > > go into commons-,
> > > along with things identified ( StopWatch?) out of commons lang and
> > > possibly
> > > other commons projects.
> > >
> > > commons-timing seems reasonable. Thoughts?
> > >
> > >
> > >
> > > On March 17, 2018 at 11:24:32, Romain Manni-Bucau
> > > (rmannibu...@gmail.com)
> > > wrote:
> > >
> > > Yes but consequence was a lack of community increase which is a
> > > killer for
> > > an incubator project on the long run.
> > >
> > > Le 17 mars 2018 15:19, "Gilles"  a
> > > écrit :
> > >
> > >> On Sat, 17 Mar 2018 12:47:40 +0100, Romain Manni-Bucau wrote:
> > >>
> > >>> Le 17 mars 2018 11:49, "Gilles"  a
> > >>> écrit :
> > >>>
> > >>> On Thu, 15 Mar 2018 15:13:39 +0100, Romain Manni-Bucau wrote:
> > >>>
> > >>> 2018-03-15 14:36 GMT+01:00 Otto Fowler :
> > 
> >  If we can come to consensus on the way forward, I’ll be happy to
> >  do the
> > 
> > > work ( although I’ll need help of course ).
> > > I guess I’m the straw that broke the camel’s back then? ;)
> > >
> > >
> > >
> > >
> > > On March 15, 2018 at 08:09:45, Gilles
> > > (gil...@harfang.homelinux.org)
> > > wrote:
> > >
> > > Hi.
> > >
> > > On Thu, 15 Mar 2018 03:52:58 -0700, Otto Fowler wrote:
> > > > I think bringing back commons-monitoring/sirota would only be
> > > > possible if
> > > > it were to be modular enough that you could bring in the ‘core’
> > > > classes
> > > > without needing to bring in all of what sirota ended up being,
> > > which
> > > > was an
> > > > end to end solution.
> > >
> > > Isn't it possible? [I didn't look; Romain should tell whether he
> > > would be interested in taking 

Re: [configuration] environment variables

[Gary Gregory]

Nevermind: org.apache.commons.configuration2.EnvironmentConfiguration

Gary

On Wed, Mar 28, 2018 at 10:04 AM, Gary Gregory 
wrote:

> Hi All:
>
> I see that Commons Configuration supports system properties but
> not environment variables.
>
> Any objection to adding support for environment variables in the same vein
> as we have for system properties?
>
> Gary
>

Re: [DISCUSS] new component for timing?

[Otto Fowler]

How about commons-timing, having StopWatch, StackWatch and other classes
that
we can find?



On March 20, 2018 at 18:40:05, Romain Manni-Bucau (rmannibu...@gmail.com)
wrote:

I would be happy to revive sirona @asf but dont think [monitoring] as just
a few classes would bring enough value compare to a lambda not worthing any
lib/dep in apps - just my opinion indeed.

For circuit breaker: geronimo safeguard can be interested in hosting that
utility part and drop failsafe dependency. Maybe something to discuss in
another thread.

Le 20 mars 2018 23:27, "Otto Fowler"  a écrit :

> Sirona is gone, it is a closed incubator project. Romain has forked it to
> his own repo.
>
>
>
> On March 20, 2018 at 18:24:06, Gilles (gil...@harfang.homelinux.org)
> wrote:
>
> On Tue, 20 Mar 2018 15:00:41 -0700, Otto Fowler wrote:
> > If monitoring was started a new, and not re-viving the old
> > monitoring?
>
> Can the feature be contributed to "Sirona"? Otto, are you
> interested in this?
> Does it make sense to have "Commons Monitoring" revived based
> on part/all of "Sirona"?
> Romain, are you interested in this?
> What would be the scope/description of "Commons Monitoring"?
>
> Noting Romain's experience that the original "Commons" project
> evolved into "Sirona", it would be strange to start from scratch
> without a plan to not follow the same route again...
>
> Gilles
>
> > On March 20, 2018 at 17:56:44, Bruno P. Kinoshita (
> > brunodepau...@yahoo.com.br.invalid) wrote:
> >
> > I think StopWatch and CircuitBreakers could be moved together to the
> > same
> > component. However, a circuit breaker can be time-related, or not
> > (e.g. a
> > circuit breaker for memory size). So probably commons-timing could be
> > a
> > good place for StopWatch, but maybe not for circuit-breaker. But I
> > think
> > both could be under commons-monitoring perhaps?
> >
> > From: Otto Fowler 
> > To: Romain Manni-Bucau ; Commons Developers
> > List <
> > dev@commons.apache.org>
> > Sent: Wednesday, 21 March 2018 10:30 AM
> > Subject: Re: [DISCUSS] new component for timing?
> >
> > I would love to get this on track. I apologize if I have made it
> > more
> > confusing than it needs to be,
> > I’m trying to be open to all the suggestions.
> >
> > If we assume that stack watch is worth ‘having’, then the question is
> > where
> > to put it.
> > commons-monitoring / sirota seems to me to be a ‘complete’ solution
> > as
> > opposed to
> > a set of or collection of like classes.
> >
> > Setting the community support / project aspect of sirota aside, it
> > seems
> > strange to put
> > a separate class into a more complete and uniform system. Unless
> > there is
> > some generically
> > useful set of timing utility classes that could be taken out of
> > sirota to
> > go into commons-,
> > along with things identified ( StopWatch?) out of commons lang and
> > possibly
> > other commons projects.
> >
> > commons-timing seems reasonable. Thoughts?
> >
> >
> >
> > On March 17, 2018 at 11:24:32, Romain Manni-Bucau
> > (rmannibu...@gmail.com)
> > wrote:
> >
> > Yes but consequence was a lack of community increase which is a
> > killer for
> > an incubator project on the long run.
> >
> > Le 17 mars 2018 15:19, "Gilles"  a
> > écrit :
> >
> >> On Sat, 17 Mar 2018 12:47:40 +0100, Romain Manni-Bucau wrote:
> >>
> >>> Le 17 mars 2018 11:49, "Gilles"  a
> >>> écrit :
> >>>
> >>> On Thu, 15 Mar 2018 15:13:39 +0100, Romain Manni-Bucau wrote:
> >>>
> >>> 2018-03-15 14:36 GMT+01:00 Otto Fowler :
> 
>  If we can come to consensus on the way forward, I’ll be happy to
>  do the
> 
> > work ( although I’ll need help of course ).
> > I guess I’m the straw that broke the camel’s back then? ;)
> >
> >
> >
> >
> > On March 15, 2018 at 08:09:45, Gilles
> > (gil...@harfang.homelinux.org)
> > wrote:
> >
> > Hi.
> >
> > On Thu, 15 Mar 2018 03:52:58 -0700, Otto Fowler wrote:
> > > I think bringing back commons-monitoring/sirota would only be
> > > possible if
> > > it were to be modular enough that you could bring in the ‘core’
> > > classes
> > > without needing to bring in all of what sirota ended up being,
> > which
> > > was an
> > > end to end solution.
> >
> > Isn't it possible? [I didn't look; Romain should tell whether he
> > would be interested in taking that route.]
> >
> >
> > Sirona was done modular, just the API, the in memory part, etc...
>  But this kind of impl needs way more just after so not sure it
>  does
> > worth
>  splitting it to put it back altogether after.
> 
>  What is the rational to try to push a very small part @commons
>  instead
> > of
>  creating a community @incubator with an E2E solution? This is what
>  I
> > fail
>  to see.

[configuration] environment variables

[Gary Gregory]

Hi All:

I see that Commons Configuration supports system properties but
not environment variables.

Any objection to adding support for environment variables in the same vein
as we have for system properties?

Gary

[GitHub] commons-imaging pull request #36: Avoid jpeg parse fail due to jfxx and exif

[hyunuck]

GitHub user hyunuck opened a pull request:

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

Avoid jpeg parse fail due to jfxx and exif

- add jfxx signature when parsing jpeg
- Avoid jpeg parse fail due to exif

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

$ git pull https://github.com/hyunuck/commons-imaging master

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

https://github.com/apache/commons-imaging/pull/36.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 #36


commit e337c954847bf3a5ff17b64ec17c45916280fe31
Author: Justin 
Date:   2018-03-28T14:41:52Z

add jfxx signature when parsing jpeg

commit 8ad11248834e21154a09fdeb9c130bd800ea8250
Author: Justin 
Date:   2018-03-28T14:44:45Z

Avoid jpeg parse fail due to exif




---

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