I would be comfortable to use a maven profile that is disabled by default
together with the plugin to do the C# build.
Any concerns with that approach?
Art
P.S. Apologies if I missed something from your messages Michael - the
spacing on my screen is a mess (looks like lost newlines).
On Tue,
So, TL;DR: I had been keeping an eye on the testsuite, and we are
clear at this point. You spotted an intermittent failure that would
fail 1 in 10 and I just fixed it.
So, we are fine. if you see any other issues please let me know here.
On Tue, Apr 7, 2020 at 9:13 PM Clebert Suconic
wrote:
>
>
I wasn't aware of the JIRA you mentioned, even though I had been
following the testsuite... and hence I fixed quite a lot of those
issues.
Recently I broke the test you mentioned, and I just sent a PR to fix it.
The testsuite has been clear to my best knowledge as of last week
after these fixes
The issues reported on ARTEMIS-2659 I fixed last week, as I had an
encoding issue for Large Messages that I fixed.
The one thing I'm not sure what's happening is on
testAcceptWithoutSettling that fails in a loop. But the test has been
clear for the past week after I fixed the encoding.
I have
I'd recommend looking into the failures documented in this issue as they
seem to indicate regressions in the AMQP protocol handler stack as
compared to the previous release which doesn't seem to reproduce these
from testing myself and Robbie have done.
I asked Justin, and he will try for it... if it's just a day or two
delay we should probably wait. if it delays any further that's what I
meant for another release in about a month.
On Tue, Apr 7, 2020 at 5:24 PM Michael Pearce wrote:
>
> Is it worth getting the queue config refactor in before
Is it worth getting the queue config refactor in before this release? That
Justin has worked on. That way we can have a release with the refactor and
then the test cases could be refactored for the following release.
On Tue, 7 Apr 2020, 17:57 Clebert Suconic,
wrote:
> I am planning a
Plugin that we use internally at work where a project is java and dotnet and
use maven to perform the build and
release.https://github.com/kaspersorensen/dotnet-maven-pluginIts apache
licensed so no issues there.Sent from my Samsung Galaxy smartphone.
Original message From:
A few things here.You can actually bind the build with maven and dotnet, theres
a maven plugin that will actually download bits needed for dotnet core and
compile and even run. This way you could actually tie it into the maven
release.Re core 3. Before anything in examples can be updated theres
not yet and thank you for your reply.
I don't have experience with Java and Maven but I do agree that it is not a
good idea to mix examples in a way I proposed before.
Answering your question regarding the C# sources, they will be built by
msbuild.
I have another idea, but it will require small
Did you get any feedback on this?
Here are thoughts that come to mind...
The src/main/java/... structure is used by (and "encouraged" by) Maven.
Would the C# sources be built as part of the maven build process? If so,
how do we ensure folks can build the Java sources even when they don't have
I am planning a release on April 13th.
and at least for the short term I want to keep a more frequent release
schedule, with another one in the first week of May. which I will send
another heads up by the end of this month.
There are a lot of good enhancements to be released now.. good fixes.
Of course I should, but right after checking out the repo I've got
thousands of changes that I didn't make, it's hard to distinguish which are
mine, and which are not. I will try to do this on Linux, hopefully with
better luck.
On Tue, Apr 7, 2020 at 10:05 AM michael.andre.pearce
wrote:
> Hi
Hi KrysztofYou should only have a change in the file you amended. And its
generated counterpart. BestMikeSent from my Samsung Galaxy smartphone.
Original message From: Krzysztof Date:
06/04/2020 19:58 (GMT+00:00) To: dev@activemq.apache.org Subject: Update
Website on Windows
14 matches
Mail list logo
