Hi,
ActiveMQ 5.16.0 will still be build with JDK8 but fully support JDK11+ at
runtime (standalone or Karaf embedded).
That’s the target and it’s fair enough.
ActiveMQ 5.17.0 will both include JMS 2.0 support + build with JDK 11.
Regards
JB
> Le 5 mars 2020 à 23:21, W B D a écrit :
>
> I
I thought it had already been decided that 5.16 would continue to support
JDK 8 but run under either JDK. I wonder if the JDK11 support could be
templated or conditionally selected with different build profiles so it
could be merged into the release branch?
On Wed, Mar 4, 2020 at 10:18 PM
Hi guys,
New update about the ActiveMQ releases.
I only have one Jira to address. It will be fixed today.
So, I plan to submit 5.15.12 to vote tonight and 5.16.0 tomorrow or during the
weekend.
Regards
JB
> Le 28 janv. 2020 à 13:57, Jean-Baptiste Onofré a écrit :
>
> Hi guys,
>
> I would
Hi guys,
Just a quick update about these releases.
Basically, I have two actions to complete before the releases:
1. Performance improvements for PostgreSQL JDBC adapter.
2. STOMP log messages cleanup/improvements
I’m fully committed and focused on these release, I will submit both to vote
Technically it's possible, but I would inform the users first.
So, 5.17.x gives us time to do so.
Regards
JB
On 29/01/2020 11:30, Colm O hEigeartaigh wrote:
> Hi all,
>
> If LevelDB is deprecated for several major versions, I'm wondering if we
> should just not remove it in 5.16.0 instead of
I am good with removing it from either but 5.17.0 might be better because
we can send out a notice to the mailing lists and give users time to
prepare in case anyone is still using it. The primary motivation to remove
it now vs leaving it is so we don't have to worry about the Scala upgrade
and
Hi all,
If LevelDB is deprecated for several major versions, I'm wondering if we
should just not remove it in 5.16.0 instead of waiting til 5.17.0?
Colm.
On Wed, Jan 29, 2020 at 5:40 AM Jean-Baptiste Onofré
wrote:
> Hi Christopher,
>
> OK, so, I will move forward on 5.16.0 with JDK11 support
Hi Christopher,
OK, so, I will move forward on 5.16.0 with JDK11 support at runtime.
I will focus on JDK11 build + LevelDB cleanup + other
cleanup/refactoring for 5.17.0.
So, let me move forward on 5.16.0 as it's now ready ;)
Regards
JB
On 28/01/2020 20:22, Christopher Shannon wrote:
> We
> On Jan 28, 2020, at 1:22 PM, Christopher Shannon
> wrote:
>
> We definitely do not want to remove JDK 8 support for 5.16.0 so my vote is
> for option 1. I think it's fine if we build with JDK 8 as long as it
> supports JDK 8 - 11 at runtime.
>
> For 5.17.0 we can work on building with
Hey JBO-
Thanks for your efforts on this. I’d like to see a JDK 11 runtime. No
preference 5.16.x v 5.17.x.
-Matt
> On Jan 28, 2020, at 6:57 AM, Jean-Baptiste Onofré wrote:
>
> Hi guys,
>
> I would like to move forward on ActiveMQ releases:
>
> - ActiveMQ 5.15.12
> I'm preparing several
On 1/28/20 2:22 PM, Christopher Shannon wrote:
We definitely do not want to remove JDK 8 support for 5.16.0 so my vote is
for option 1. I think it's fine if we build with JDK 8 as long as it
supports JDK 8 - 11 at runtime.
For 5.17.0 we can work on building with JDK 11. For one thing I think
We definitely do not want to remove JDK 8 support for 5.16.0 so my vote is
for option 1. I think it's fine if we build with JDK 8 as long as it
supports JDK 8 - 11 at runtime.
For 5.17.0 we can work on building with JDK 11. For one thing I think we
should just make it easier on ourselves and
Hi guys,
I would like to move forward on ActiveMQ releases:
- ActiveMQ 5.15.12
I'm preparing several dependency updates and important fixes on the
activemq-5.15.x branch. It includes some security fixes, postgresql jdbc
store performance improvements, ...
I have some PRs under review and on the
13 matches
Mail list logo
