Re: [DISCUSS] Merge JPMS work in upcoming maven-compiler-plugin beta-2

Is there any technical reason why we could not port those ? Le mer. 23 oct. 2024 à 22:46, Jorge Solórzano a écrit : > Without delving into every detail, one concern I have is the inability to > use the option alongside and , MCOMPILER-582 >

Re: [DISCUSS] Merge JPMS work in upcoming maven-compiler-plugin beta-2

I wonder if the changes have been ported to surefire and javadoc? Or maybe not needed as no impact? Sorry just a question from the peanut gallery (as I didn't have a look at the changes). But I remember suffering (because I was more involved at this time) a lot of issues in the past when JPMS was i

Re: [DISCUSS] Project member emeritus policy change

+-0 but maybe start to setup a routine which will generate a "team2.html" page with a column "latest contribution" (mail or commit or review?) and from there see how it looks like and then spawn again the emeritus topic? Romain Manni-Bucau @rmannibucau | Blog

Re: [Committer School] Stephen, Arnaud & Barrie's school for potential Maven committers does this still exist?

And thanks a lot Elliotte for catching it It's a really important effort to give some love to our docs On Thu, Oct 24, 2024 at 12:08 AM Arnaud Héritier wrote: > > https://github.com/apache/maven-site/commit/416f0d6a515d7c3aa8c3ea5d39c90c0b5422eb26 > should do it > > On Wed, Oct 23, 2024 at 11:59

Re: [Committer School] Stephen, Arnaud & Barrie's school for potential Maven committers does this still exist?

https://github.com/apache/maven-site/commit/416f0d6a515d7c3aa8c3ea5d39c90c0b5422eb26 should do it On Wed, Oct 23, 2024 at 11:59 PM Arnaud Héritier wrote: > whaou > Good old memories but now. > That's probably more than a decade old :-/ > I don't think we got a lot of traction. > It predates

Re: [DISCUSS] Project member emeritus policy change

+1 On Tue, Oct 22, 2024 at 6:17 PM Tamás Cservenák wrote: > Howdy, > > I would like to propose a project policy change (followed by > implementation) regarding "emeritus" status of PMCs and members. > > Proposal: > 1) IF a PMC member is inactive for 24 months (did NOT participate in > any VOTE [

Re: [Committer School] Stephen, Arnaud & Barrie's school for potential Maven committers does this still exist?

whaou Good old memories but now. That's probably more than a decade old :-/ I don't think we got a lot of traction. It predates what could be done today as Google Summer of Code It's ok to delete it Thanks On Wed, Oct 23, 2024 at 11:42 PM Elliotte Rusty Harold wrote: > Stumbled across thi

[Committer School] Stephen, Arnaud & Barrie's school for potential Maven committers does this still exist?

Stumbled across this in our docs today: https://maven.apache.org/guides/development/guide-committer-school I would like to become a committer and the Message body: I am interested in the following areas: ___, ___ and __ If anyone knows any issues that I could take a look at I would

Re: [DISCUSS] Merge JPMS work in upcoming maven-compiler-plugin beta-2

Without delving into every detail, one concern I have is the inability to use the option alongside and , MCOMPILER-582 was a nice improvement, but I'm not sure if that behavior remains. In any case, in my opinion, relying on an empty workaro

Re: [DISCUSS] Project member emeritus policy change

Supply chain attacks are a concern. In practice I've never heard of one of these coming about because of old committer account compromise. I have seen them happen because: 1. A threat actor actively targets a project and becomes a coimmitter by submitting good patches over time. 2. An entire proj

Re: [DISCUSS] Project member emeritus policy change

If the goal here is to simply clarify the metrics on project participation, perhaps we could run one of the tools from CHAOSS that will tell us how many people participate and how (mail list, commits, reviews, etc.) On Wed, Oct 23, 2024 at 3:20 PM Ralph Goers wrote: > FWIW, if Maven adopts the i

Re: [DISCUSS] Merge JPMS work in upcoming maven-compiler-plugin beta-2

Le 2024-10-23 à 16 h 22, Ralph Goers a écrit : What is the easiest way to determine what has been changed? When I was working on Log4j’s JPMS support Maven’s handling of JPMS frequently caused problems and forced us to do some things I consider kind of ugly. The main changes are described the

Re: [DISCUSS] Merge JPMS work in upcoming maven-compiler-plugin beta-2

What is the easiest way to determine what has been changed? When I was working on Log4j’s JPMS support Maven’s handling of JPMS frequently caused problems and forced us to do some things I consider kind of ugly. Ralph > On Oct 23, 2024, at 7:12 AM, Guillaume Nodet wrote: > > Following the b

Re: [DISCUSS] Project member emeritus policy change

FWIW, if Maven adopts the idea of modifying https://maven.apache.org/team.html similar to the Logging Services team page I linked too then I would likely move myself to the inactive list. Although I do occasionally participate in threads like this and vote on occasion I haven’t committed to the

[DISCUSS] Merge JPMS work in upcoming maven-compiler-plugin beta-2

Following the beta-5 release, we're going to update a bunch of plugins (help welcome to port a few core plugins). In particular, I think the maven-compiler-plugin would benefit from a merge of Martin Deruisseaux's work around JPMS [1]. This leverages the javax.tools API directly, so will remove th

[PR] Bump maven.version from 4.0.0-beta-4 to 4.0.0-beta-5 [maven-xinclude-extension]

dependabot[bot] opened a new pull request, #12: URL: https://github.com/apache/maven-xinclude-extension/pull/12 Bumps `maven.version` from 4.0.0-beta-4 to 4.0.0-beta-5. Updates `org.apache.maven:maven-api-core` from 4.0.0-beta-4 to 4.0.0-beta-5 Updates `org.apache.maven:maven-api-di

[PR] Bump com.fasterxml.woodstox:woodstox-core from 7.0.0 to 7.1.0 [maven-xinclude-extension]

dependabot[bot] opened a new pull request, #13: URL: https://github.com/apache/maven-xinclude-extension/pull/13 Bumps [com.fasterxml.woodstox:woodstox-core](https://github.com/FasterXML/woodstox) from 7.0.0 to 7.1.0. Commits https://github.com/FasterXML/woodstox/commit/1fdedb1

Re: [DISCUSS] Project member emeritus policy change

+1 Regarding the "dormant PMC member" issue that Eliotte mentioned. I am happy people are willing to contribute again! From what I understand, an inactive member is only marked as inactive / emeritus. They are not removed from the PMC. They can become active again by simply contributing and

Re: [DISCUSS] Enable GitHub issues and GitHub discussions

> Am 22.10.2024 um 16:52 schrieb Guillaume Nodet : > > I'd like to start discussing opening (and eventually slowly switching) from > JIRA to GitHub issues. > > JIRA is a bit of a pain to use, even though we have some automatic links > done with PRs and such. Accounts need to be authorized to ma