Re: Toolchains and Maven Enforcer

2025-02-04 Thread Guillaume Nodet
Le mar. 4 févr. 2025 à 09:05, Thomas Reinhardt a écrit : > > Interesting, I was not aware of the new discovery mechanism. > > Unfortunately the most interesting goal "select-jdk-toolchain" is not > marked threadsafe. Was that a conscious decision or just easier to > implement? > I think it's an

Re: [VOTE] Release Maven Resolver Ant Tasks 1.5.2

2025-02-04 Thread Arnaud Héritier
+1 Arnaud Héritier Twitter/GitHub/ASF... : aheritier On Tue, Feb 4, 2025 at 22:00 Sylwester Lachiewicz wrote: > +1 > > wt., 4 lut 2025, 21:49 użytkownik Olivier Lamy napisał: > > > +1 > > On Mon, 3 Feb 2025 at 1:22 am, Tamás Cservenák > > wrote: > > > > > Howdy, > > > > > > We solved 5 issue

Re: Github issue migration problem

2025-02-04 Thread Benjamin Marwell
We are on contact with GitHub support. Please refrain from manually closing them for now. Before that, some were not displayed, were in status pending, which effectively made them missing. I'll keep you posted. On Tue, 4 Feb 2025, 23:44 Elliotte Rusty Harold, wrote: > If you look at https://

Re: Github issue migration problem

2025-02-04 Thread Slawomir Jaranowski
I'm still not convitient if we really need copy all issues from jira to github - as I wrote many times - jira will be exist with us - I don't believe that users before creating new issue look for old - if yes they have a link to old issues - many issues should be triaged again - it is manually wor

Re: Github issue migration problem

2025-02-04 Thread Guillaume Nodet
Le mer. 5 févr. 2025 à 07:36, Slawomir Jaranowski a écrit : > I'm still not convitient if we really need copy all issues from jira > to github - as I wrote many times > > - jira will be exist with us > - I don't believe that users before creating new issue look for old - > if yes they have a link

Re: Github issue migration problem

2025-02-04 Thread Herve Boutemy
if we don't copy, we can't search in one place: I'm often searching in issues to get why we did something in the past (that years later looks strange, but history helps understand) I'd love to let some time to try before admitting we can't keep it simple in one single place once migrated Regar

Amendment proposal to

2025-02-04 Thread Martin Desruisseaux
Hello all Maven 4 introduced some new types of JAR, including: * jar (same as Maven 3) * modular-jar * classpath-jar * processor * classpath-processor * modular-processor It has been pointed out (in a discussion elsewhere about JPMS) that declaring that a JAR is for use by the annotation

Re: Amendment proposal to

2025-02-04 Thread Romain Manni-Bucau
Hi Martin, there are still processors which are runtime jars, would you make them declared twice and deduplicated by maven for relevant phases/scopes? Romain Manni-Bucau @rmannibucau | .NET Blog | Blog

Re: Amendment proposal to

2025-02-04 Thread Martin Desruisseaux
Le 2025-02-04 à 16 h 27, Romain Manni-Bucau a écrit : there are still processors which are runtime jars, would you make them declared twice and deduplicated by maven for relevant phases/scopes? The same JAR file which would need to be both on the class-path and on the annotation processor pa

Re: Toolchains and Maven Enforcer

2025-02-04 Thread Thomas Reinhardt
Interesting, I was not aware of the new discovery mechanism. Unfortunately the most interesting goal "select-jdk-toolchain" is not marked threadsafe. Was that a conscious decision or just easier to implement? Also I am missing a parameter to provide a search path. Might come in handy in CI

Re: [VOTE] Release Maven Resolver Ant Tasks 1.5.2

2025-02-04 Thread Tamás Cservenák
+1 On Sun, Feb 2, 2025 at 4:22 PM Tamás Cservenák wrote: > > Howdy, > > We solved 5 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628&version=12354742 > > There is one issue in JIRA: > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRESOLVER%20AND%20s

Re: [VOTE] Release Maven Resolver Ant Tasks 1.5.2

2025-02-04 Thread Slawomir Jaranowski
+1 On Sun, 2 Feb 2025 at 16:22, Tamás Cservenák wrote: > > Howdy, > > We solved 5 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628&version=12354742 > > There is one issue in JIRA: > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRESOLVER%20AND%20sta

Re: Amendment proposal to

2025-02-04 Thread Romain Manni-Bucau
Hmm, ok, just means we should maybe rush in supporting type or scope sets in plugins instead of having so much hardcoded defaults cause these are common cases (similarly having an artifact available for some compiling execution, some build plugin but nothing else). Thanks for confirming. Le mar.

Github issue migration problem

2025-02-04 Thread Elliotte Rusty Harold
If you look at https://github.com/apache/maven-jlink-plugin/issues you'll notice that all the issues from the Jira have been copied into github multiple times. -- Elliotte Rusty Harold elh...@ibiblio.org - To unsubscribe, e-mail

Maven plugins: compiler, install, deploy - GitHub Issues

2025-02-04 Thread Slawomir Jaranowski
Hi, I will be working on compiler, install, deploy plugins to prepare and switch to GitHub issues ... First I will fix release-drafter configuration such we maintain two version - master for Maven 4.x - branch for Maven 3.x Probably I need disable jenkins on master due to missing Maven beta, r

Re: [VOTE] Release Maven Resolver Ant Tasks 1.5.2

2025-02-04 Thread Olivier Lamy
+1 On Mon, 3 Feb 2025 at 1:22 am, Tamás Cservenák wrote: > Howdy, > > We solved 5 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628&version=12354742 > > There is one issue in JIRA: > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRESOLVER%20AND%2

Re: [VOTE] Release Maven Resolver Ant Tasks 1.5.2

2025-02-04 Thread Sylwester Lachiewicz
+1 wt., 4 lut 2025, 21:49 użytkownik Olivier Lamy napisał: > +1 > On Mon, 3 Feb 2025 at 1:22 am, Tamás Cservenák > wrote: > > > Howdy, > > > > We solved 5 issues: > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628&version=12354742 > > > > There is one issue in J

Re: Toolchains and Maven Enforcer

2025-02-04 Thread Romain Manni-Bucau
Hi, The discovery uses JAVA_xx_HOME environment variables which is often the way CI are setting up the paths - ack not on jenkins if not done manually but it is not a bad practise. I assume adding a property to configure yet another search path ( https://github.com/apache/maven-toolchains-plugin/b