Injecting JUnit-4 Parallel Execution Parameters in Surefire Plugin

2022-11-29 Thread Kamalpreet Kaur
Hi Everyone,

I'm currently creating a package from where I would want to set JUnit
parallel execution parameters like below :

*classesAndMethods
1
1
false*

I'm planning to use Instrumentation API to inject these parameters. I tried
to find the correct place where I can do so, but failed to find one.

Please point me to a class from where these values are being honoured So
that I could inject these parameters there. You could also suggest a way to
set these values apart from adding them to the  element.

I tried intercepting different surefire classes like ForkedBooter,
JUnit4Provider, JUnitCoreProvider but after that the execution didn't
happen according to specified parameters.

--
Thanks & Regards
Kamalpreet Kaur


Care to comment to InfoQ on the Spring Initializer's switch to Gradle as the default?

2022-11-29 Thread Karsten Silz
Hi!

I’m not sure if this is the right place to ask. Please let me know if I should 
post this someplace else!

I’m writing a news item for InfoQ about the Spring Initializer's switch to 
Gradle as the default: https://github.com/spring-io/start.spring.io/issues/1012 
 I’d like to get the 
input of the Maven team on that decision. 

If you agree to participate, I’d send about 5-10 questions by email. The 
questions and your answers would then appear in the news item as the official 
Maven response. I may not include all questions. 

We’re making the same offer to the Gradle team.

Please let me if you’d like to answer my questions - and where to send my 
questions in that case. Thank you! 


Regards,
Karsten Silz
InfoQ Java editor



Re: Care to comment to InfoQ on the Spring Initializer's switch to Gradle as the default?

2022-11-29 Thread Lasse Lindqvist
Hi. You might want to target d...@maven.apache.org if you are looking for
Maven developers specifically, BUT if you are looking at an "official"
response you might need to ask specific people. Check
https://maven.apache.org/team.html for the members.

(Personally I would say Gradle is to Maven what Kotlin is to Java. Drives
innovation, but is doomed to lose in the long run as long as Maven keeps
adopting features from it)

ti 29. marrask. 2022 klo 19.07 Karsten Silz (karsten.s...@gmail.com)
kirjoitti:

> Hi!
>
> I’m not sure if this is the right place to ask. Please let me know if I
> should post this someplace else!
>
> I’m writing a news item for InfoQ about the Spring Initializer's switch to
> Gradle as the default:
> https://github.com/spring-io/start.spring.io/issues/1012 <
> https://github.com/spring-io/start.spring.io/issues/1012> I’d like to get
> the input of the Maven team on that decision.
>
> If you agree to participate, I’d send about 5-10 questions by email. The
> questions and your answers would then appear in the news item as the
> official Maven response. I may not include all questions.
>
> We’re making the same offer to the Gradle team.
>
> Please let me if you’d like to answer my questions - and where to send my
> questions in that case. Thank you!
>
>
> Regards,
> Karsten Silz
> InfoQ Java editor
>
>


[ANN] Apache Maven Doxia Sitetools 2.0.0-M4 released

2022-11-29 Thread Michael Osipov
The Apache Maven team is pleased to announce the release of the Apache 
Maven Doxia Sitetools, version 2.0.0-M4


Doxia Sitetools is an extension of base Doxia component that generates 
text markup, consisting of decoration and content that was generated by 
Doxia.


https://maven.apache.org/doxia/doxia-sitetools/

You can download the appropriate sources etc. from the download page:

https://maven.apache.org/doxia/doxia-sitetools/download.cgi


Release Notes - Maven Doxia Sitetools - Version 2.0.0-M4

** Bug
* [DOXIASITETOOLS-266] - Don't create anchors behind the user's back

** Improvement
* [DOXIASITETOOLS-268] - Don't open version resource file on every 
call to render
* [DOXIASITETOOLS-271] - Overhaul locale support (make Locale#ROOT 
instead of Locale#ENGLISH default and use full locale)


** Task
* [DOXIASITETOOLS-270] - Remove internal (pseudo) skin and use 
Maven Fluido Skin by default


** Dependency upgrade
* [DOXIASITETOOLS-267] - Upgrade to Doxia 2.0.0-M4
* [DOXIASITETOOLS-273] - Upgrade Plexus Utils to 3.5.0
* [DOXIASITETOOLS-274] - Upgrade htmlunit to 2.67.0
* [DOXIASITETOOLS-275] - Upgrade Maven Reporting API to 4.0.0-M3
* [DOXIASITETOOLS-276] - Upgrade Maven Wagon to 3.5.2
* [DOXIASITETOOLS-277] - Upgrade L10N Maven Plugin to 1.0.0


Enjoy,

-The Apache Maven team

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



[ANN] Release Maven Dependency Plugin 3.4.0 released

2022-11-29 Thread Michael Osipov
The Apache Maven team is pleased to announce the release of the Maven 
Dependency Plugin version 3.4.0.


https://maven.apache.org/plugins/maven-dependency-plugin/

You should specify the version in your project's plugin configuration:


  org.apache.maven.plugins
  maven-dependency-plugin
  3.4.0



Release Notes - Maven Dependency Plugin - Version 3.4.0

** Bug
* [MDEP-806] - Dependency tree in verbose mode for war is empty
* [MDEP-809] - Javadoc was not updated to reflect that :tree's 
verbose option is now ok


** New Feature
* [MDEP-782] - Add a  option to unpack goals
* [MDEP-804] - Allow auto-ignore of all non-test scoped 
dependencies used only in test scope


** Improvement
* [MDEP-602] - Turn warnings into errors instead of failOnWarning
* [MDEP-674] - maven-dependency-plugin should leverage 
plexus-build-api to support IDEs

* [MDEP-716] - TestListClassesMojo logs too much
* [MDEP-827] - Use outputDirectory from AbstractMavenReport

** Dependency upgrade
* [MDEP-813] - Require Maven 3.2.5
* [MDEP-814] - Bump mrm-maven-plugin from 1.2.0 to 1.4.1
* [MDEP-815] - Upgrade Parent to 37
* [MDEP-817] - Bump maven-common-artifact-filters from 3.2.0 to 3.3.1
* [MDEP-818] - Bump plexus-io from 3.2.0 to 3.4.0
* [MDEP-821] - Bump mockito-core from 4.3.1 to 4.7.0
* [MDEP-822] - Bump maven-dependency-tree from 3.1.0 to 3.2.1
* [MDEP-823] - Bump maven-dependency-analyzer from 1.12.0 to 1.13.0
* [MDEP-824] - Bump plexus-utils from 3.4.1 to 3.5.0
* [MDEP-825] - Bump mockito-core from 4.7.0 to 4.9.0
* [MDEP-826] - Upgrade maven-reporting-impl from 3.1.0 to 3.2.0
* [MDEP-834] - Bump maven-common-artifact-filters from 3.3.1 to 3.3.2
* [MDEP-836] - Bump plexus-archiver from 4.2.2 to 4.6.0


Enjoy,

-The Apache Maven team

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org