@Guenter, it won't make it into the 1.1.x series
However, no big deal for us to run a 1.2.0-alpha.1 somewhat soon - there
was some talks about that on our dev list as well...
-M
On Tue, Jan 12, 2016 at 10:54 AM, Matthias Wessendorf <matzew(a)apache.org>
wrote:
cool, will do.
PR will come soon ;)
On Tuesday, 12 January 2016, gklein <gunther.klein(a)f24.com> wrote:
> Hi!
>
> Thanks for your replies. I think a system property would be perferrable
> and
> sufficient in our case. Additional ui support is nice to have.
>
> Can you file the jira ticket for me please. I would have to sign up first.
> Here is the description:
> ----
>
> Aerogear UPS 1.1.0 collects outdated push message infos in a batch job
> (calls to PushMessageMetricsService#deleteOutdatedPushInformationData).
> The
> outdated criteria is currently hardcoded to 30 days
> (PushMessageMetricsService#DAYS_OF_MAX_OLDEST_INFO_MSG). This time should
> be
> made configurable via system property. If the system property is not set
> the
> default value (30 days) should be used.
>
> ---
>
> Regards, Gunther Klein
>
>
>
> --
> View this message in context:
>
http://aerogear-users.1116366.n5.nabble.com/Aerogear-UPS-1-1-0-Feature-re...
> Sent from the aerogear-users mailing list archive at
Nabble.com.
> _______________________________________________
> Aerogear-users mailing list
> Aerogear-users(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/aerogear-users
>
--
Sent from Gmail Mobile