what's nice about this, is that even compatibility tests are
running... (think about that the compatibility tests is mixing a mesh
that includes even old hornetq clients against artemis master, and
these were built with older JDK).
I was afraid old versions of netty woudln't be compatible on the
I am able to build with adoptopenjdk 11, but not with 13. a lot of
errors on javadoc.
We would need to fix those to be able to be flexible enough? or is
there any magic settings perhaps to relax this?
On Wed, Jun 3, 2020 at 6:16 AM Robbie Gemmell wrote:
>
> Going back to the error-prone dep
> For Core messages, it appears there is a way to check the provenance of a
message.
That's correct.
> For AMQP messages, it appears there is no way to currently do this.
That's also correct.
> ...the question is how the product in question can get similar
provenance/security information for
that's probably something you can do with a Plugin or Interceptor.
On Wed, Jun 3, 2020 at 12:02 PM Dirkjan Ochtman wrote:
>
> On Wed, Jun 3, 2020 at 5:47 PM Justin Bertram wrote:
>
> > > I would like to better understand how this is supposed to work...
> >
> > What specifically do you not
On Wed, Jun 3, 2020 at 5:47 PM Justin Bertram wrote:
> > I would like to better understand how this is supposed to work...
>
> What specifically do you not understand?
>
For Core messages, it appears there is a way to check the provenance of a
message. For AMQP messages, it appears there is no
> I would like to better understand how this is supposed to work...
What specifically do you not understand?
> ...and see if there are any improvements that could be made here.
I imagine improvements could be made, but that question is pretty vague.
Are you referring specifically to your
Hi there,
I posted in ARTEMIS-2751 about how one might check the provenance of
incoming AMQP messages, but so far haven't seen any response. I would like
to better understand how this is supposed to work and see if there are any
improvements that could be made here.
Kind regards,
Dirkjan
I just post straight to the list. I don’t think you should be using
babble.
On Wed, Jun 3, 2020 at 9:13 AM Domenico Francesco Bruscino <
bruscin...@gmail.com> wrote:
> Hi,
>
> when I try to create a new topic using nabble
>
> http://activemq.2283324.n4.nabble.com/ActiveMQ-Dev-f2368404.html
>
Hi,
when I try to create a new topic using nabble
http://activemq.2283324.n4.nabble.com/ActiveMQ-Dev-f2368404.html
http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
I get the following error:
You Cannot Post Here
Sorry, but you can't create new topics here.
Note that you may
Hi Emmanuel,
Even if I’m French my locale is always en_US ;)
So I didn’t notice such build failure, let me check.
Regards
JB
> Le 3 juin 2020 à 11:43, Emmanuel Hugonnet a écrit :
>
> Hello,
>
> Sorry I'm French so my locale is FR_fr which makes the current build fails.
>
> Failed tests:
>
Going back to the error-prone dep being added to all the modules, if
those need to stay I think it would be good for the scope+optional
elements be added as well? I see its being governed in the
dependencyManagement addition, but the various modules appear to have
those elements for their existing
Can I ask again about the seemingly broken errorprone-javac config on
the branch, which looks to be using a non-existent javac.version
property config:
"-J-Xbootclasspath/p:${settings.localRepository}/com/google/errorprone/javac/${javac.version}/javac-${javac.version}.jar
Looking at
Hello,
Sorry I'm French so my locale is FR_fr which makes the current build fails.
Failed tests:
HumanReadableByteCountTest.test:31 expected:<999[.]0B> but was:<999[,]0B>
As you can see this is a really simple failure, that can be easily fixed but
I'm wondering about some side effects
13 matches
Mail list logo
