[VOTE] Release Apache Maven Reporting API version 4.0.0-M3

Hi, We solved 2 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922&version=12352562 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHARED%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20m

Re: Maven and the Path API

That's done in the v4 api. Le mer. 23 nov. 2022 à 19:37, Christoph Läubrich a écrit : > Currently maven is bound to the Java File API, e.g. > > org.apache.maven.project.MavenProject.getBasedir() > org.apache.maven.project.MavenProject.getFile() > > while others uses Strings, e.g. > > org.apache.

Re: [VOTE] Release Maven Resolver 1.9.2

Am 2022-11-23 um 13:56 schrieb Tamás Cservenák: Howdy, We solved 2 issues: https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRESOLVER%20AND%20fixVersion%20%3D%201.9.2 20fixVersion%20%3D%201.9.1

Maven and the Path API

Currently maven is bound to the Java File API, e.g. org.apache.maven.project.MavenProject.getBasedir() org.apache.maven.project.MavenProject.getFile() while others uses Strings, e.g. org.apache.maven.project.MavenProject.addCompileSourceRoot(String) I wonder if it would be good to move Maven t

[GitHub] [maven-shared-incremental] dependabot[bot] opened a new pull request, #16: Bump maven-shared-components from 37 to 38

dependabot[bot] opened a new pull request, #16: URL: https://github.com/apache/maven-shared-incremental/pull/16 Bumps [maven-shared-components](https://github.com/apache/maven-parent) from 37 to 38. Release notes Sourced from https://github.com/apache/maven-parent/releases";>maven-

Re: [DISCUSS] Notes For Maven Plugin Developers

So org.apache.maven.repository.RepositorySystem - should be deprecated ... śr., 23 lis 2022 o 14:53 Tamás Cservenák napisał(a): > Howdy, > > Sorry for the late reply. > > Yes, original plan was to ditch maven-compat (for 4.0.0), but then it > turned out that in "maven 3 universe", to do some s

Re: [VOTE] Release Maven Resolver 1.9.2

+1 śr., 23 lis 2022 o 13:57 Tamás Cservenák napisał(a): > Howdy, > > We solved 2 issues: > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRESOLVER%20AND%20fixVersion%20%3D%201.9.2 > 20fixVersion%20%3D%201.9.1 > < > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRES

Re: [DISCUSS] Notes For Maven Plugin Developers

Howdy, Sorry for the late reply. Yes, original plan was to ditch maven-compat (for 4.0.0), but then it turned out that in "maven 3 universe", to do some stuff you had two options: - either rely on something in maven-compat - or reach directly for resolver (but it was not "popular" choice due 3.0/

Re: [DISCUSS] Speed up release process?

Le mer. 23 nov. 2022 à 14:38, Romain Manni-Bucau a écrit : > To answer the typical/atypical point: I guess maven is atypically typical > ;). > There are multiple projects like that, from Geronimo (even if it gets > better these days) to the OSGi projects (aries, smix, ...), even TomEE at > some p

Re: [DISCUSS] Speed up release process?

To answer the typical/atypical point: I guess maven is atypically typical ;). There are multiple projects like that, from Geronimo (even if it gets better these days) to the OSGi projects (aries, smix, ...), even TomEE at some point which was releasing its own ~350 modules + 5-6 forks (to get quick

Re: Polyglot usage of components/Dependency graph API

Yep, which means that the executioncontext of the plugin should also switch to the right tccl probably as you mentionned. Romain Manni-Bucau @rmannibucau | Blog | Old Blog | Github

Re: [DISCUSS] Speed up release process?

Tamas, Il giorno mer 23 nov 2022 alle ore 14:22 Tamás Cservenák ha scritto: > > Romain, > > Ok, I accept your response. > > Would be interested about feedback for the rest of 152 projects... :) > (actually not, is rhetorical really, just shows my point) > > As I still stand with my conclusion: "M

Re: Polyglot usage of components/Dependency graph API

Right, so there are 3 important realms. realm coreExtension>io.takari.polyglot:polyglot-ruby:0.4.7 is what I assume is loaded from .mvn/extensions.xml, and is the parent classloader of Ruby. realm extension>org.apache.felix:maven-bundle-plugin:4.2.1 is weird in that it can resolve the class, but d

Re: [DISCUSS] Speed up release process?

Romain, Ok, I accept your response. Would be interested about feedback for the rest of 152 projects... :) (actually not, is rhetorical really, just shows my point) As I still stand with my conclusion: "Maven might be quite atypical ASF project by juggling with many more artifacts than others".

Re: Polyglot usage of components/Dependency graph API

The TCCL of the plugin should be the plugin classloader, in all other cases it will likely just fail without any hack (like stealing the right classloader). I'm not sure I fully get your table - or if gmail misformatted it - but if it is a plain plugin declaration this should be ok, if declared as

[VOTE] Release Maven Resolver 1.9.2

Howdy, We solved 2 issues: https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRESOLVER%20AND%20fixVersion%20%3D%201.9.2 20fixVersion%20%3D%201.9.1 There are still some issues in JIRA:

Re: Polyglot usage of components/Dependency graph API

Both that and trying to simply get the Class. After some investigation, I made a table with the below code: matchR,matchT,loadclass,.lookup(), realm .. .. ..!Ex! , for realm plexus.core PARENT .. ..!Ex! , for realm coreExtension>io.takari.polyglot:polyglot-rub