Re: [ANN] Maven Surefire 3.2.1 released
Just have upgraded this plugin whithout any issues :)
from mobile (sorry for typos ;)
On Wed, Oct 25, 2023, 19:30 Garret Wilson wrote:
> Could you clarify whether this means that the plugin will not work
> correctly, and whether we should wait for a patch version that uses the
> correct dependencies instead of upgrading our POMs to use this announced
> version 3.2.1?
>
> Thanks,
>
> Garret
>
> On 10/24/2023 7:42 AM, Thomas Broyer wrote:
> > This is using plexus-xml 4.0.0 (from Parent 40). Shouldn't that be
> > downgraded to 3.0.0?
> > (
> >
> https://github.com/apache/maven-parent/commit/096de2d1f79a1b692a112db16675ecc2ac013597
> > says 4.0.0 is not compatible with Maven 3; maybe a Parent 41 should have
> > been released after that commit?)
> >
> > Fwiw, I have a plugin that depends on surefire-common (maybe it shouldn't
> > but that's another story) and this brings maven-xml-impl et al. that are
> > flagged as not being in the correct scope (brought in as "compile",
> should
> > be "provided"). My tests pass with that version, but I've explicitly
> > downgraded to 3.0.0 (upgraded plexus-utils to 4.0.0 and added dependency
> on
> > plexus-xml 3.0.0) and tests still pass, so I think I'm going to go with
> > that.
> >
> > On Mon, Oct 23, 2023 at 10:00 PM Michael Osipov
> wrote:
> >
> >> The Apache Maven team is pleased to announce the release of the Maven
> >> Surefire version 3.2.1.
> >>
> >> https://maven.apache.org/surefire/
> >>
> >>
> >> Release Notes - Maven Surefire - Version 3.2.1
> >>
> >> ** Bug
> >> * [SUREFIRE-2190] - optional dependencies and JPMS modules confuse
> >> surefire
> >> * [SUREFIRE-2196] -
> >> maven-surefire-report-plugin:failsafe-report-only failed: Unmatched
> >> braces in the pattern
> >> * [SUREFIRE-2202] - NullPointerException if super class meets
> >> specific condition
> >>
> >> ** New Feature
> >> * [SUREFIRE-1124] - Let ${surefire.forkNumber} deliver unique
> >> environmentVariables when used in parallel mvn builds
> >>
> >> ** Improvement
> >> * [SUREFIRE-2177] - Use junit-bom instead of single JUnit 5
> versions
> >> * [SUREFIRE-2178] - classpathDependencyExcludes should support
> >> classifiers
> >> * [SUREFIRE-2179] - additionalClasspathElements should support
> >> Maven coordinates
> >> * [SUREFIRE-2182] - Log starter implementation on DEBUG level
> >>
> >> ** Dependency upgrade
> >> * [SUREFIRE-2188] - Upgrade to Parent 40
> >>
> >>
> >> Enjoy,
> >>
> >> -The Apache Maven team
> >>
> >> -
> >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> >> For additional commands, e-mail: users-h...@maven.apache.org
> >>
> >>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>
Re: [ANN] Maven Surefire 3.2.1 released
Could you clarify whether this means that the plugin will not work
correctly, and whether we should wait for a patch version that uses the
correct dependencies instead of upgrading our POMs to use this announced
version 3.2.1?
Thanks,
Garret
On 10/24/2023 7:42 AM, Thomas Broyer wrote:
This is using plexus-xml 4.0.0 (from Parent 40). Shouldn't that be
downgraded to 3.0.0?
(
https://github.com/apache/maven-parent/commit/096de2d1f79a1b692a112db16675ecc2ac013597
says 4.0.0 is not compatible with Maven 3; maybe a Parent 41 should have
been released after that commit?)
Fwiw, I have a plugin that depends on surefire-common (maybe it shouldn't
but that's another story) and this brings maven-xml-impl et al. that are
flagged as not being in the correct scope (brought in as "compile", should
be "provided"). My tests pass with that version, but I've explicitly
downgraded to 3.0.0 (upgraded plexus-utils to 4.0.0 and added dependency on
plexus-xml 3.0.0) and tests still pass, so I think I'm going to go with
that.
On Mon, Oct 23, 2023 at 10:00 PM Michael Osipov wrote:
The Apache Maven team is pleased to announce the release of the Maven
Surefire version 3.2.1.
https://maven.apache.org/surefire/
Release Notes - Maven Surefire - Version 3.2.1
** Bug
* [SUREFIRE-2190] - optional dependencies and JPMS modules confuse
surefire
* [SUREFIRE-2196] -
maven-surefire-report-plugin:failsafe-report-only failed: Unmatched
braces in the pattern
* [SUREFIRE-2202] - NullPointerException if super class meets
specific condition
** New Feature
* [SUREFIRE-1124] - Let ${surefire.forkNumber} deliver unique
environmentVariables when used in parallel mvn builds
** Improvement
* [SUREFIRE-2177] - Use junit-bom instead of single JUnit 5 versions
* [SUREFIRE-2178] - classpathDependencyExcludes should support
classifiers
* [SUREFIRE-2179] - additionalClasspathElements should support
Maven coordinates
* [SUREFIRE-2182] - Log starter implementation on DEBUG level
** Dependency upgrade
* [SUREFIRE-2188] - Upgrade to Parent 40
Enjoy,
-The Apache Maven team
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: [ANN] Maven Surefire 3.2.1 released
Good catch. This crept in in other builds as well :-(
On 2023/10/24 10:42:33 Thomas Broyer wrote:
> This is using plexus-xml 4.0.0 (from Parent 40). Shouldn't that be
> downgraded to 3.0.0?
> (
> https://github.com/apache/maven-parent/commit/096de2d1f79a1b692a112db16675ecc2ac013597
> says 4.0.0 is not compatible with Maven 3; maybe a Parent 41 should have
> been released after that commit?)
>
> Fwiw, I have a plugin that depends on surefire-common (maybe it shouldn't
> but that's another story) and this brings maven-xml-impl et al. that are
> flagged as not being in the correct scope (brought in as "compile", should
> be "provided"). My tests pass with that version, but I've explicitly
> downgraded to 3.0.0 (upgraded plexus-utils to 4.0.0 and added dependency on
> plexus-xml 3.0.0) and tests still pass, so I think I'm going to go with
> that.
>
> On Mon, Oct 23, 2023 at 10:00 PM Michael Osipov wrote:
>
> > The Apache Maven team is pleased to announce the release of the Maven
> > Surefire version 3.2.1.
> >
> > https://maven.apache.org/surefire/
> >
> >
> > Release Notes - Maven Surefire - Version 3.2.1
> >
> > ** Bug
> > * [SUREFIRE-2190] - optional dependencies and JPMS modules confuse
> > surefire
> > * [SUREFIRE-2196] -
> > maven-surefire-report-plugin:failsafe-report-only failed: Unmatched
> > braces in the pattern
> > * [SUREFIRE-2202] - NullPointerException if super class meets
> > specific condition
> >
> > ** New Feature
> > * [SUREFIRE-1124] - Let ${surefire.forkNumber} deliver unique
> > environmentVariables when used in parallel mvn builds
> >
> > ** Improvement
> > * [SUREFIRE-2177] - Use junit-bom instead of single JUnit 5 versions
> > * [SUREFIRE-2178] - classpathDependencyExcludes should support
> > classifiers
> > * [SUREFIRE-2179] - additionalClasspathElements should support
> > Maven coordinates
> > * [SUREFIRE-2182] - Log starter implementation on DEBUG level
> >
> > ** Dependency upgrade
> > * [SUREFIRE-2188] - Upgrade to Parent 40
> >
> >
> > Enjoy,
> >
> > -The Apache Maven team
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> > For additional commands, e-mail: users-h...@maven.apache.org
> >
> >
>
> --
> Thomas Broyer
> /tɔ.ma.bʁwa.je/
Re: [ANN] Maven Surefire 3.2.1 released
This is using plexus-xml 4.0.0 (from Parent 40). Shouldn't that be
downgraded to 3.0.0?
(
https://github.com/apache/maven-parent/commit/096de2d1f79a1b692a112db16675ecc2ac013597
says 4.0.0 is not compatible with Maven 3; maybe a Parent 41 should have
been released after that commit?)
Fwiw, I have a plugin that depends on surefire-common (maybe it shouldn't
but that's another story) and this brings maven-xml-impl et al. that are
flagged as not being in the correct scope (brought in as "compile", should
be "provided"). My tests pass with that version, but I've explicitly
downgraded to 3.0.0 (upgraded plexus-utils to 4.0.0 and added dependency on
plexus-xml 3.0.0) and tests still pass, so I think I'm going to go with
that.
On Mon, Oct 23, 2023 at 10:00 PM Michael Osipov wrote:
> The Apache Maven team is pleased to announce the release of the Maven
> Surefire version 3.2.1.
>
> https://maven.apache.org/surefire/
>
>
> Release Notes - Maven Surefire - Version 3.2.1
>
> ** Bug
> * [SUREFIRE-2190] - optional dependencies and JPMS modules confuse
> surefire
> * [SUREFIRE-2196] -
> maven-surefire-report-plugin:failsafe-report-only failed: Unmatched
> braces in the pattern
> * [SUREFIRE-2202] - NullPointerException if super class meets
> specific condition
>
> ** New Feature
> * [SUREFIRE-1124] - Let ${surefire.forkNumber} deliver unique
> environmentVariables when used in parallel mvn builds
>
> ** Improvement
> * [SUREFIRE-2177] - Use junit-bom instead of single JUnit 5 versions
> * [SUREFIRE-2178] - classpathDependencyExcludes should support
> classifiers
> * [SUREFIRE-2179] - additionalClasspathElements should support
> Maven coordinates
> * [SUREFIRE-2182] - Log starter implementation on DEBUG level
>
> ** Dependency upgrade
> * [SUREFIRE-2188] - Upgrade to Parent 40
>
>
> Enjoy,
>
> -The Apache Maven team
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>
--
Thomas Broyer
/tɔ.ma.bʁwa.je/
[ANN] Maven Surefire 3.2.1 released
The Apache Maven team is pleased to announce the release of the Maven
Surefire version 3.2.1.
https://maven.apache.org/surefire/
Release Notes - Maven Surefire - Version 3.2.1
** Bug
* [SUREFIRE-2190] - optional dependencies and JPMS modules confuse
surefire
* [SUREFIRE-2196] -
maven-surefire-report-plugin:failsafe-report-only failed: Unmatched
braces in the pattern
* [SUREFIRE-2202] - NullPointerException if super class meets
specific condition
** New Feature
* [SUREFIRE-1124] - Let ${surefire.forkNumber} deliver unique
environmentVariables when used in parallel mvn builds
** Improvement
* [SUREFIRE-2177] - Use junit-bom instead of single JUnit 5 versions
* [SUREFIRE-2178] - classpathDependencyExcludes should support
classifiers
* [SUREFIRE-2179] - additionalClasspathElements should support
Maven coordinates
* [SUREFIRE-2182] - Log starter implementation on DEBUG level
** Dependency upgrade
* [SUREFIRE-2188] - Upgrade to Parent 40
Enjoy,
-The Apache Maven team
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
