Hi Tibor,
I'm happy to help. Please see here for my current progress
https://github.com/apache/maven-surefire/compare/master...mlambert:master.
Prior to raising a pull request I was planning to:
* Add more test cases
* Test these changes with a local maven project - I'm hoping it will be as
Am 2020-07-13 um 10:24 schrieb :
You should try to ask less one single mail. Split your questions.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
On 2020/07/13 17:03:21, Nigel Jones wrote:
> I'm getting an error when building an assembly. mvn is 3.6.3 and plugins are
> up to date (we use dependabot to keep them that way, along with
> pluginManagement)
In case it helps here are the full versions of some of my files
I'm getting an error when building an assembly. mvn is 3.6.3 and plugins are up
to date (we use dependabot to keep them that way, along with pluginManagement)
[WARNING] The following patterns were never triggered in this artifact
inclusion filter:
o
The Maven team is pleased to announce the release of the Apache Maven WAR
Plugin, version 3.3.1
This plugin builds a Web Application Archive (WAR) file from the project output
and its dependencies.
https://maven.apache.org/plugins/maven-war-plugin/
You should specify the version in your
Can you elaborate more?
On Mon, Jul 13, 2020 at 5:08 PM 不才 wrote:
>
>
>
That is correct, Martin. If not told otherwise, Maven would resort to
the default bindings, as Tamás explained. I don't know why it defaults
to a relatively old version in this case, maybe someone else on the list
knows.
My approach would be to pin those versions in the pluginManagement
section
So if not told otherwise, in plugin management, maven ist defaulting back to?
https://github.com/apache/maven/blob/master/maven-core/src/main/resources/META-INF/plexus/default-bindings.xml
Wow, I'm deeply surprised.
So, what is the recommended way to work with that? Is there a way to change the
