I don't expect any issues with 13-ea. I've already used it during my talks.
Since the plugin is pretty stable after several major release of Java, I
don't expect another plugin release soon, so better spend some time on
MCOMPILER-320[1] too.
Right now there's a fork, but it would be better to
On Mon, 25 Mar 2019 11:35:04 +0100, Bradley Atkins
wrote:
All,
When looking at forking and updating maven-source-plugin to get rid of
it's dependency on the vulnerable package - org.codehaus.plexus :
plexus-utils
What's the vulnerability?
I found that these packages are also using
Thanks for having a look Tibor!
On Mon, Mar 25, 2019 at 4:37 PM Tibor Digana wrote:
> The diff looks good.
>
> Stephane, I guess this only 50% work you wanted to have.
>
I wanted to make sure that the JUnit5 story was functional with the vintage
engine and the current GA of surefire. It looks
The diff looks good.
Stephane, I guess this only 50% work you wanted to have.
Let's not make too many versions because this would be a precedent.
Question about JUnit5 display name. Currently our solution turns XML file
name and XML content to the textual display name and not fully qualified
I'll check the diff.
On Mon, Mar 25, 2019 at 3:38 PM Stephane Nicoll
wrote:
> Hey,
>
> Can someone working on surefire confirm the interest of creating that
> branch in the main repo and kick-off a release if a review is satisfactory?
>
> Thanks!
> S.
>
>
> On Wed, Mar 13, 2019 at 4:09 PM
Hey,
Can someone working on surefire confirm the interest of creating that
branch in the main repo and kick-off a release if a review is satisfactory?
Thanks!
S.
On Wed, Mar 13, 2019 at 4:09 PM Stephane Nicoll
wrote:
> Hey,
>
> I've created a `2.22.x` branch based on the 2.22.1 tag and I've
Il lun 25 mar 2019, 00:19 Tibor Digana ha scritto:
> Hi Dejan,
>
> Good to hear. In our Jira are two issues related to my original email:
> https://issues.apache.org/jira/browse/SUREFIRE-1654
> https://issues.apache.org/jira/browse/SUREFIRE-1494
> If you have any questions, feel free to ask
