Re: [DISCUSS] Support YAML poms

nate that this currently depends on the not yet released Maven 4 rc3…. Konrad > On 5. Mar 2025, at 17:16, Guillaume Nodet wrote: > > Hey ! > > A while ago, I created a Hocon based POM parser [1], leveraging Maven > 4 new capabilities to support new syntaxes for POMs. >

Re: [HEADS UP] Parent POMs ASF 34 and Maven 44

All Doxia fixes were for the Markdown Sink which is not relevant for m-site-p but just for converting to MD format. So I don’t think we need to wait. Konrad > On 3. Mar 2025, at 21:51, Sylwester Lachiewicz wrote: > > Konrad, are we ok with the current Doxia 2 or do we need one mor

Re: Leveraging SonarQube Cloud (fka SonarCloud)

Leveraging Automatic Analysis cannot calculate code coverage. Therefore the option with two different GHAs should be used (as outlined in https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=321719166#GitHubActionsSecurity-Buildstriggeredwithworkflow_run). Regards, Konrad > O

Re: Using git forks

-permissions-for-github_token#changing-the-permissions-in-a-forked-repository) which might affect PR decoration and other stuff. Are you sure that everything related to building PRs works just as well in forks? Konrad > On 4. Jan 2025, at 15:14, Tamás Cservenák wrote: > > Howdy, > &

Leveraging SonarQube Cloud (fka SonarCloud)

improve the code quality and gives some pointers on PR quality. WDYT about enabling this for https://github.com/apache/maven? Regards, Konrad - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands

[ANN] Apache Maven Fluido Skin 2.0.1 Released

The Apache Maven team is pleased to announce the release of the Maven Fluido Skin, version 2.0.1. https://maven.apache.org/skins/maven-fluido-skin/ You should specify the version in your project's site configuration: org.apache.maven.skins maven-fluido-skin 2.0.1 Import: This release requ

[RESULT] [VOTE] Release Apache Maven Fluido Skin version 2.0.1

Hi, The vote has passed with the following result: +1 : Sylwester, Tamás, Sławomir, Michael PMC quorum was reached. I will promote the source release zip file to Apache distribution area and the artifacts to the central repo. Thanks for voting, Konrad > On 6. Dec 2024, at 17:11, Kon

repository.apache.org and Nexus 2 EOL

Maven Central publishing should work in the future for large organisations like ASF? Thanks for some input on this matter Konrad

[VOTE] Release Apache Maven Fluido Skin version 2.0.1

ance for voting, Konrad - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org

Re: Future of palantir / spotless in Maven

I am a bit worried by https://github.com/palantir/palantir-java-format/issues/735. Although I know that also the Google Formatter suffers from this, I am not sure how resilient that is with respect to future JDK updates. Konrad > On 29. Nov 2024, at 10:33, Piotr P. Karwasz wrote: >

Re: [VOTE] Release Maven Fluido Skin version 2.0.0-M11

+1 The mentioned issue with spotless on source-release.zip is an overall issue with https://maven.apache.org/pom/maven/, and therefore I reported this in https://github.com/apache/maven-parent/issues/205. It does not block the release from my perspective. Thanks, Konrad > On 26. Sep 2024,

Re: [VOTE] Release Maven Fluido Skin version 2.0.0-M11

Hi, I just did that with https://github.com/diffplug/spotless/issues/2277. Konrad > On 26. Sep 2024, at 12:05, Michael Osipov wrote: > > Am 2024-09-26 um 11:59 schrieb Konrad Windszus: >> It works when I add >> …. >> >> >> >> com.diffplug.spo

Re: [VOTE] Release Maven Fluido Skin version 2.0.0-M11

pom.xml included in the source-archive.jar? I don’t see an easy way to fix this right now. Konrad > On 26. Sep 2024, at 11:45, Konrad Windszus wrote: > > I cannot rebuild from the source-release.zip. > When building with "mvn package" I get errors from spotless: > > [INF

Re: [VOTE] Release Maven Fluido Skin version 2.0.0-M11

cdc97d260186937) Maven home: /opt/homebrew/Cellar/maven/3.9.9/libexec Java version: 11.0.24, vendor: Eclipse Adoptium, runtime: /Library/Java/JavaVirtualMachines/temurin-11.jdk/Contents/Home Default locale: en_DE, platform encoding: UTF-8 OS name: "mac os x", version: "14.7", arc

Re: [ANN] Apache Maven Daemon 1.0.2 released

Probably it is time now to add the formula to homebrew/core (https://docs.brew.sh/Acceptable-Formulae). I think we satisfy the requirements there... > On 11. Sep 2024, at 14:02, Konrad Windszus wrote: > > Hi, > The homebrew tap is still at 1.0.1 > (https://github.com/mvndaemo

Re: [ANN] Apache Maven Daemon 1.0.2 released

https://github.com/apache/maven-mvnd?tab=readme-ov-file#install-using-homebrew, though. I don’t think all ASF committers have write access to the repo, so there is gap here. Thanks for any thoughts on this. Konrad > On 24. Aug 2024, at 12:47, Tamás Cservenák wrote: > > The Apache M

Re: [RESULT] [VOTE] Release Apache Maven Filtering 3.4.0

Hi Basil, Both should be updated now, I just didn’t find the time before. Thanks for the pointer, Konrad > On 10. Sep 2024, at 02:26, Basil Crow wrote: > > Was this release successful? I am getting Dependabot updates for > 3.4.0, but I cannot find any release notes on GitHub

[ANN] Apache Maven Filtering 3.4.0 Released

The Apache Maven team is pleased to announce the release of the Apache Maven Filtering 3.4.0 https://maven.apache.org/shared/maven-filtering/ Release Notes - Maven Shared Components - Version maven-filtering-3.4.0 ** Improvement * [MSHARED-1412] - Allow customization of Interpolator used fo

Re: Inheritance of Report Sets

Hi, How does this prevent running the reports for the parent itself? Konrad > On 8. Sep 2024, at 09:12, Michael Osipov wrote: > > Am 2024-09-06 um 11:06 schrieb Konrad Windszus: >> Hi, >> Unlike plugin (with plugin management and its configuration) the reportSet >>

Inheritance of Report Sets

on the current project and inheriting ones. What I want to achieve is a common report set for all children without being active on the parent itself. Any idea? Thanks in advance, Konrad - To unsubscribe, e-mail: dev-unsubscr

Disable ASF GitHub Bot comments in JIRA

erve: Since you added it explicitly via e.g. https://github.com/apache/maven-release/commit/78e2329b2aee142563d5fd93feda216e04662bdc or https://github.com/apache/maven-site-plugin/commit/75c8d35df293a4e0defa5c7ac1092c7984e0f93d I am wondering what the intention was…. WDYT? Konrad [1] - h

[VOTE] Release Apache Maven Filtering 3.4.0

s: https://maven.apache.org/guides/development/guide-testing-releases.html Vote open for at least 72 hours. [ ] +1 [ ] +0 [ ] -1 Thanks in advance for checking the release, Konrad - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For ad

Re: [VOTE] Release Maven Plugin Tools version 3.15.0

It is actually 5 issues in total: https://issues.apache.org/jira/browse/MPLUGIN-530 was missing because I set an incorrect fix version on the JIRA originally. Hope this doesn’t have an impact on anyone’s vote. Sorry for this, Konrad > On 22. Aug 2024, at 19:17, Michael Osipov wrote: >

Re: [DISCUSS] maven-core-plugin

nk would be candidate to the merge? > Any "LOT of code duplication" that is found elsewhere? > > > on evaluating the value we get from it: > as a Maven dev, it's true that clean, install and deploy have few releases. > Resources seem to have a current issue r

Maven Resolver inconsistency between VersionRangeResult and VersionResult

for the former? I know parsing is necessary for the latter to ensure correct ordering. Thanks for some pointers, Konrad [1] - https://github.com/apache/maven-resolver/blob/362a43675f01b8bb3d85d7b0ff76a21d57de6fee/maven-resolver-api/src/main/java/org/eclipse/aether/resolution/VersionResult.java

Re: [DISCUSS] maven-core-plugin

:35, Konrad Windszus wrote: > > Hi, > Although I do see the benefits from a Maven Dev perspective for Consumers > this is worse. > In the past often individual plugin versions suffered from regressions for > certain edge cases. > > Having individual separate plugins allowe

Re: [DISCUSS] maven-core-plugin

(e.g. maven-resources-plugin) while upgrading all others to the latest version available. One example is maven-resources-plugin which suffered from some regressions in the past. Instead I would rather try to identify the shared code and put it into a library (new or existing). Konrad > On 15.

Re: [VOTE] Release Maven Plugin Tools version 3.14.0

/MojoAnnotationsScanner.java#L40 Was the intention of https://issues.apache.org/jira/browse/MPLUGIN-523 only the creation of the branches without cleaning up the code? Thanks for some insights, Konrad > On 14. Aug 2024, at 17:47, Michael Osipov wrote: > > Hi, > > we solved 2

Re: Terminology proposal: "Maven module" -> "Maven sub-project"

the renaming here. Konrad > On 5. Aug 2024, at 14:14, Martin Desruisseaux > wrote: > > In order to avoid confusion between "Maven module" and "Java module", I > suggest to update documentation for using "Maven sub-project" instead of > "

Re: GH Action Shared v4 fails for Java 8 on Mac OS

I have never seen a case yet where it works on Mac OS Aarch64 Java but fails on Mac OS x64 Java (or vice versa). Once we have that we can think about adding more Mac OS versions. For me what matters is that we cover Mac OS at all (no matter if with Aarch64 or X64). Konrad > On 11. Aug 2024,

Re: GH Action Shared v4 fails for Java 8 on Mac OS

Sorry for the noise, turned out that PR still used the v3 version of the Shared GH action. V4 is already configured to use Azul by default (https://github.com/apache/maven-gh-actions-shared/commit/994eebd0d7acb406c055aed405b32ca42415df91) With v4 it is working fine. Konrad > On 11. Aug 2

GH Action Shared v4 fails for Java 8 on Mac OS

cOS-latest node in GitHub is now a Aarch64 machine (https://github.com/actions/runner-images?tab=readme-ov-file#available-images) for which there is no Temurin 8 distribution. Potential solutions: 1) Use Azul for Mac OS with Java 8 2) Skip Java 8 build on Mac OS WDYT? Than

Re: How to use Sisu components in Mojos

I created https://issues.apache.org/jira/browse/MPLUGIN-530 to track this. On 2024/06/17 11:43:30 Konrad Windszus wrote: > Is there any downside with > https://maven.apache.org/ref/3.9.8/maven-plugin-api/plugin.html#class_requirement > no longer being maintained? > How does the e

Re: Status of new compiler plugin for Maven 4

/eclipse/compiler/GroovyEclipseCompiler.java#L71C14-L71C35) which doesn’t implement javax.tools.JavaCompiler (yet). I opened https://github.com/groovy/groovy-eclipse/issues/1592 to raise an improvement request regarding this. Konrad > On 23. Jul 2024, at 10:58, Martin Desruisseaux > wrote: &

[ANN] Apache Resource Bundles 1.7 Released

The Apache Maven team is pleased to announce the release of the Apache Resource Bundles, version 1.7 https://maven.apache.org/apache-resource-bundles/ Release Notes - Apache Maven Resource Bundles - Version 1.7 ** Bug * [MASFRES-69] - All files having a filename containing "target" are ex

[RESULT] [VOTE] Release Apache Resource Bundles 1.7

Hi, The vote has passed with the following result: +1 : Olivier, Sylwester, Karl Heinz PMC quorum: reached I will promote the source release zip file to Apache distribution area and the artifacts to the central repo. Thanks for voting, Konrad

Re: Site of maven-war-plugin

heckin for project Apache Maven WAR Plugin @Michael: Any idea? My guess is the site was non deliberately pushed from a SNAPSHOT branch…. Thanks, Konrad > On 24. Jul 2024, at 07:15, Karl Heinz Marbaise > wrote: > > Hi to all, > > I've realized that the current page

[VOTE] Release Apache Resource Bundles 1.7

Hi, We solved 5 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314621&version=12353102&styleName=Text Staging repo: https://repository.apache.org/content/repositories/orgapacheapache-1040/ https://repository.apache.org/content/repositories/orgapacheapache-1040/org/a

Re: [VOTE] Release Apache Resource Bundles 1.6

Both were newer than the initial vote email. One of it is fixing the regression which lead to cancelling the vote. Konrad > On 20. Jul 2024, at 11:22, Michael Osipov wrote: > > There are two open PRs from you. Wouldn't it be better to review and merge > them before

[CANCEL] [VOTE] Release Apache Resource Bundles 1.6

Hi, Unfortunately there is a regression with the fix from https://issues.apache.org/jira/browse/MASFRES-69. I am therefore cancelling this release and will spin a new one, once I have a proper fix. Thanks, Konrad > On 19. Jul 2024, at 11:40, Konrad Windszus wrote: > > Sorry, my ma

Re: [VOTE] Release Apache Resource Bundles 1.6

-testing-releases.html Vote open for at least 72 hours. [ ] +1 [ ] +0 [ ] -1 > On 19. Jul 2024, at 11:37, Konrad Windszus wrote: > > Hi, > > We solved 4 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314621&version=12353102&styleName=Tex

[VOTE] Release Apache Resource Bundles 1.6

Hi, We solved 4 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314621&version=12353102&styleName=Text Staging repo: https://repository.apache.org/content/re

Re: How to use Sisu components in Mojos

/maven/plugin/descriptor/Requirement.java#L25C14-L25C25, WDYT @Guillaume? Thanks, Konrad > On 17. Jun 2024, at 13:25, Konrad Windszus wrote: > > > Hi, > I am wondering about the best practice to inject Sisu/JSR330 components into > Mojos. > We have two different possi

How to use Sisu components in Mojos

descriptor [3]. 2. Via the JSR330 Inject annotation For the former I couldn’t find a way to use multi bindings [2] but the latter does not affect the plugin descriptor [3], therefore error handling might be inferior. Any opinions/thoughts? Thanks in advance, Konrad [1] - https://maven.apache.org

Re: [VOTE] Release Maven Site Plugin version 4.0.0-M14

Maven 4 API. So should we rename this to m-site-p 3.13.x? This requires adaptation in the source code with regards to the since javadoc tag. WDYT? Konrad > On 5. May 2024, at 21:29, Michael Osipov wrote: > > Hi, > > we solved 4 issues: > https://issues.apache.org/jira/secur

Re: [VOTE] Release Maven SCM version 2.1.0

+1 Konrad > On 11. Apr 2024, at 15:18, Michael Osipov wrote: > > Hi, > > We solved 11 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317828&version=12354448 > > There are still a couple of issues left in JIRA: > https://issues.apac

Re: [VOTE] Release Maven Doxia version 2.0.0-M10

+1 Konrad > On 11. Apr 2024, at 14:17, Michael Osipov wrote: > > Hi, > > we solved 10 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317230&version=12354136 > > There are still a couple of issues left in JIRA: > https://issues.apac

Re: [DISCUSS] Eclipse wiki shutting down re Aether (MRESOLVER-289)

Done and export attached to the new https://issues.apache.org/jira/browse/MRESOLVER-526. Can you pick it up from there? Thanks, Konrad > On 10. Apr 2024, at 14:24, Tamás Cservenák wrote: > > Konrad, > > Could you sort this out? (asking for export) > > Thanks > T >

Re: [DISCUSS] Eclipse wiki shutting down re Aether (MRESOLVER-289)

Hi, I think almost everything is helpful for consumers (although probably needs a bit tweaking/updating). The only thing I would not migrate is - https://wiki.eclipse.org/Aether/New_and_Noteworthy and - https://wiki.eclipse.org/Aether itself Can we get an MD export? Konrad > On 10. Apr 2

Revert commit 740dae43ca3ccf7692f37edf3184387e5666ca6b

referenced ticket https://issues.apache.org/jira/browse/MNG-4840 is only about the prerequisites section in the POM. Herve can you revert please? I propose to use PRs (even for changes like this) to prevent mistakes like this. Thanks, Konrad

Re: [VOTE] Release Apache Maven Doxia Sitetools version 2.0.0-M17

and validation before spinning a release. Konrad > On 12. Mar 2024, at 16:29, Konrad Windszus wrote: > > HI, > For me the site build of > https://github.com/apache/jackrabbit-filevault-package-maven-plugin fails > with Sitetools 2.0.0-M17 > > "[

Re: [VOTE] Release Apache Maven Doxia Sitetools version 2.0.0-M17

me here, because I committed the responsible code pieces. Konrad > On 9. Mar 2024, at 21:38, Michael Osipov wrote: > > Hi, > > we solved 7 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317320&version=12354091 > > There are still a co

Re: [DISCUSS] Maven Core Plugins versioning

maintained by the Apache Maven Project (not only core plugin according to the definition from above). Konrad > On 6. Mar 2024, at 15:12, Tamás Cservenák wrote: > > Gary, > > maven "core plugins" are these > https://maven.apache.org/plugins/ > > In short, Maven p

Re: [DISCUSS] Maven Core Plugins versioning

Maven Core plugins are listed in https://maven.apache.org/plugins/. But I would say that this versioning policy applies to all plugins in groupId org.apache.maven.plugins….. Konrad > On 6. Mar 2024, at 15:06, Gary Gregory wrote: > > One issue from a non-Maven dev (me) is that I hav

Re: [DISCUSS] Maven Core Plugins versioning

extraordinary case would probably justify a change of the artifactId. Konrad > On 6. Mar 2024, at 14:58, Tamás Cservenák wrote: > > Howdy, > > We have several topics that need to be discussed. > > I. Core Plugin Versioning > > History: When Maven2 was born, and starte

Re: [VOTE] Require Java 17 for Maven 4

+1 Konrad > On 28. Feb 2024, at 08:30, Benjamin Marwell wrote: > > Hi Maven Devs/Users/Committers and PMC members! > > After several discussions on the mailing lists, I would like to > start a vote in favour of setting the minimal Java bytecode target > of Maven-Core 4 to

Re: Using .git-blame-ignore-revs with reordered lines

Ping, does anyone have any input on this? Would be much appreciated, Thanks, Konrad > On 8. Jan 2024, at 19:16, Konrad Windszus wrote: > > Hi, > > According to https://maven.apache.org/pom/maven/#the-format-profile the git > commits created through applying the spotless fo

Using .git-blame-ignore-revs with reordered lines

-ignore-revs. WDYT? Konrad - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org

Re: [VOTE] Release Maven Doxia version 2.0.0-M9

correctly here?) Thanks for taking care of the release Konrad > On 6. Jan 2024, at 21:22, Michael Osipov wrote: > > Hi, > > we solved 12 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317230&version=12354052 > > There are still a couple of

Re: Plugins documentations - improvements

/plugin/plugin/report/GoalRenderer.java for details. If you propose something in a PR I will happily review. Probably at the same time we should get rid of required vs optional as required often comes with a default value… Konrad > On 23. Dec 2023, at 22:00, Michael Osipov wrote: > >

MSKINS-229

(again) to another project. It is a regression from a user’s perspective because TOCs worked with 1.x and do no longer with 2.x. For me supporting generating a TOC is crucial and we shouldn’t drop this support in 2.x therefore just considering this invalid feels wrong to me. Konrad > Be

Re: [VOTE] Release Apache Maven Reporting Exec version 2.0.0-M12

great to make some progress here, We suffer from this on our Maven Site currently (e.g. in https://maven.apache.org/guides/introduction/introduction-to-profiles.html where the TOC is broken) so a fix for this is quite urgent to me. Konrad > On 24. Nov 2023, at 22:11, Michael Osipov wr

Re: injecting an object for plugin configuration on Maven CLI

Hi, Only the value classes listed in https://maven.apache.org/guides/mini/guide-configuring-plugins.html#Mapping_Value_Objects support conversion from string. There is nothing built in for complex classes containing multiple values of different types. Konrad > On 17. Nov 2023, at 08:51, He

Re: [VOTE] Release Maven Resolver 2.0.0-alpha-1

The resolver API is only containing classes below org.eclipse.aether for historical reasons: https://github.com/apache/maven-resolver/tree/master/maven-resolver-api/src Konrad > On 6. Nov 2023, at 13:13, Elliotte Rusty Harold wrote: > > -1 > > I see at least one issue

Re: [VOTE] Release Maven Plugin Tools version 3.10.1

apart from the colouring)? Konrad > On 19. Oct 2023, at 09:20, Michael Osipov wrote: > > Went through the two cases, I believe that they are fine (or more logical > than before): > > 1. Change in link style: > before: >> >> <fast> >> > >

Using Sink API with XHTML markup

, Konrad [1] - https://issues.apache.org/jira/browse/MPLUGIN-442 [2] - https://maven.apache.org/doxia/developers/sink.html#avoid-sink-rawtext - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail

Re: [maven-source-plugin] 3.3.0 incompatible with 3.2.1

> PS: There is also a typo in the error message: maven-source-plugn -> > maven-source-plugin > Reported and fixed already in master: https://github.com/apache/maven-source-plugin/commit/1edeea47f80bc5c5903e88c1adbff56501248a8b

Re: [maven-source-plugin] 3.3.0 incompatible with 3.2.1

JIRA issue. Thanks, Konrad > On 15. Aug 2023, at 19:48, Gary Gregory wrote: > > On Tue, Aug 15, 2023 at 12:42 PM Michael Osipov <mailto:micha...@apache.org>> wrote: >> >> Am 2023-08-15 um 14:57 schrieb Gary Gregory: >>> Hi All, >>> >>&g

Re: [VOTE] Change to the voting process

Not allowed, according to https://www.apache.org/foundation/voting.html#ReleaseVotes "the 'minimum quorum of three +1 votes' rule is universal." On 2023/05/12 10:01:12 Tamás Cservenák wrote: > Howdy, > > Lazy consensus? > > Again, my main goal is to stir voters up. > And if unclear, of course I

Re: [VOTE] Change to the voting process

I don't expect more votes even if increasing the minimum timeframe. Also what really matters is binding votes, so only PMC members count (which brings the number down to < 30). Konrad On 2023/05/12 09:31:34 Tamás Cservenák wrote: > Howdy, > > I'd like to propose a c

Re: [VOTE] Change to the voting process

-1 on that proposal. As said before every release manager can decide to wait longer than 72 hours. But for some releases (urgent hotfixes) waiting 30 days until pushing it is just not acceptable (IMHO). Konrad On 2023/05/12 09:31:34 Tamás Cservenák wrote: > Howdy, > > I'd lik

Re: [HEADS UP] ASF/Maven parent poms

I agree with that. For me a new ASF parent release is primarily necessary due to the fact that using the current version leads to quite some warnings when used with Maven 3.9.1. On 2023/04/15 12:31:07 Slawomir Jaranowski wrote: > sob., 15 kwi 2023 o 12:40 Michael Osipov napisał(a): > > > Am 2

Deprecate maven-shared-utils

and potentially can be easily added to plexus utils. WDYT? Konrad

Re: 4.0 alpha javadocs

Look at https://github.com/apache/maven/blob/master/plexus-utils/README.md for the reasoning. Konrad On 2022/11/25 12:13:29 Elliotte Rusty Harold wrote: > Random question. why are we publishing codehaus packages in the Maven > Javadocs? > > https://maven.apache.org/ref/4.0.0-alp

Re: Maven 3 API, backwards compatibility

is was intended. I added a PR for enforcing binary compatibility with Maven 3.8.6 and saw plenty of incompatibilities, details in https://github.com/apache/maven/pull/874. Konrad - To unsubscribe, e-mail: dev-unsubscr...@maven.apac

Re: Maven 3 API, backwards compatibility

moved a method on an interface which may have been implemented by extensions...) Konrad On 2022/11/16 09:35:15 Tamás Cservenák wrote: > Unsure we want to deprecate all of Maven :) > > But yes, in general, 3.x "Maven API" was "all that users can grab" sadly, >

Re: Maven 3 API, backwards compatibility

I see now there is already https://github.com/apache/maven/blob/master/api/maven-api-meta/src/main/java/org/apache/maven/api/annotations/Provider.java but to me the javadoc is not explicit enough. It should state: Only Maven is allowed to implement/extend types with this annotation. Konrad On

Maven 3 API, backwards compatibility

t.java#L29> or https://wiki.eclipse.org/API_Javadoc_tags#The_New_Solution <https://wiki.eclipse.org/API_Javadoc_tags#The_New_Solution> WDYT? Konrad

Re: [VOTE] Release Maven Plugin Tools 3.7.0

+1 (non-binding). Tested successfully with some Maven plugins. Konrad On 2022/10/30 10:02:21 Slawomir Jaranowski wrote: > Hi, > > We solved 42 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317820&version=12344367 > > There are still a co

Re: [VOTE] Release Maven Plugin Tools 3.7.0

Hi, I created https://issues.apache.org/jira/browse/MPLUGIN-429 and https://issues.apache.org/jira/browse/MPLUGIN-428 for the superfluous warnings related to missing Javadoc URLs. Sorry that this slipped through. Konrad > too many examples for this plugin broken links [1] I don'

Re: Improve connection between Maven and IDE?

, but for the mid term I would pretty much suggest that we keep the useful plexus-builds-utils and try to evolve it just a bit as I don't see any other viable alternative. Konrad - To unsubscribe, e-mail: dev-unsubscr

Re: Improve connection between Maven and IDE?

The API exists since 2009, so we are not talking about a new thing here. Also some things IMHO cannot be expressed with plain Mojo/Maven API (like line number, column or file where error/warning occurred). So let's focus the discussion rather on the concrete API/proposal for extension. K

Re: [ANN] Apache Maven Verifier 2.0.0-M1 Released

R-85/1/pipeline. It tried replacing "aether-transport-wagon" by "aether-transport-http" but it still fails. I can only reproduce with the more complicated ASF Jenkins setup which runs ITs separately, but wagon used to work with Maven Verifier 1.

Re: Improve connection between Maven and IDE?

Probably a misunderstanding then. It sounded a bit like you deny the benefit of having an API for incremental builds and IDE integration in general. But good that we are on the same page that as an opt-in API this is definitely a good thing to have. Konrad

Re: [ANN] Apache Maven Verifier 2.0.0-M1 Released

org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:263) ... 114 more Any idea what may have caused this? Do I need to adjust other dependencies? Thanks in advance for any pointers, Konrad - To

Re: Improve connection between Maven and IDE?

ou can update the links at https://www.eclipse.org/m2e/documentation/m2e-making-maven-plugins-compat.html#buildcontext to point to the current repo. Konrad - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For addi

Re: [VOTE] Release Apache Maven Daemon 0.8.1

Sounds good to me, I will watch for release candidate 0.8.2 then... Thanks. Konrad > On 19. Sep 2022, at 16:08, Guillaume Nodet wrote: > > I'd be more confident if everything was raised to the same level. > I propose to close this vote and cut another release later this week wi

Re: [VOTE] Release Apache Maven Daemon 0.8.1

the GH build to version 22.2.0. I can build the 0.8.1 tag with 22.2.0 and then upload to https://dist.apache.org/repos/dist/dev/maven/mvnd/0.8.1/. Are you fine with that approach? Thanks, Konrad > On 19. Sep 2022, at 14:34, Guillaume Nodet wrote: > > Sorry for the delay. I think t

Re: ASF Source Assembly now contains .gitignore and .gitattributes

82758ec0f5e0269e/src/main/java/org/codehaus/plexus/util/AbstractScanner.java#L55 even further... Konrad - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org

Re: ASF Source Assembly now contains .gitignore and .gitattributes

of Archiver a real superset of the default excludes of p-u Scanner (and therefore also the derived PlexusIoFileResourceCollection. WDYT? Konrad - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional com

ASF Source Assembly now contains .gitignore and .gitattributes

the same excludes should be applied to maven-source-plugin which currently also only relies on plexus-utils default excludes. WDYT? Konrad - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-

Re: [VOTE] Release Apache Maven Daemon 0.8.1

I can offer to manually build a Mac OS aarch64 binary and push it to the dist folder. WDYT? Konrad On 2022/09/08 13:13:28 Guillaume Nodet wrote: > I've staged a candidate release at > https://dist.apache.org/repos/dist/dev/maven/mvnd/0.8.1/ > > The changelog is availa

Re: Replacements for ArtifactMetadataSource

/aether/RepositorySystem.java#L191. Hope this helps, Konrad On 2022/08/21 11:08:35 Slawomir Jaranowski wrote: > Hi, > > Tamás, can you provide the full class name ... > > I found it: > https://maven.apache.org/resolver/apidocs/org/eclipse/aether/impl/VersionResolver.html > but

Re: API for resolving Maven artifacts to be used from Mojos

/apache/maven/api/services/ArtifactResolver.java. Konrad On 2022/08/15 07:10:58 Konrad Windszus wrote: > Hi, > I found the following APIs dealing with resolving of Maven artifacts: > > 1. > https://maven.apache.org/ref/3.8.6/apidocs/org/apache/maven/repository/RepositorySystem.htm

API for resolving Maven artifacts to be used from Mojos

around it. Thanks in advance for any pointers. Konrad - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org

Re: more details plugin requirements

> > But the documentation doesn't mention it > > https://maven.apache.org/plugins/maven-deploy-plugin/plugin-info.html > > This is autogenerated. Adding such information is not possible. > This can be adjusted via https://maven.apache.org/plugin-tools/maven-plugin-plugin/report-mojo.html#requ

Re: Mojo parameters of type java.nio.file.Path

)? Thanks, Konrad On 2022/07/31 09:40:27 Stuart McCulloch wrote: > That's correct, Maven still uses the Plexus configuration API to convert > XML configuration to mojo parameters. > > Sisu looks for the best matching converter as follows for Plexus > configuration requ

Re: Mojo parameters of type java.nio.file.Path

Containers API for Maven 4? Thanks, Konrad On 2022/07/29 17:17:30 Tamás Cservenák wrote: > Don't mix in plexus (is dead). You need Guice spi TypeConverter. > > T > > On Fri, Jul 29, 2022, 16:22 Romain Manni-Bucau > wrote: > > > Hi Konrad, > > > > Gue

Re: Mojo parameters of type java.nio.file.Path

://issues.apache.org/jira/browse/MNG-7524. Thanks, Konrad On 2022/07/29 14:27:05 Jorge Solórzano wrote: > Hi Konrad, > > If I'm not wrong, Eclipse Sisu handles the conversion of parameters, so yes > right now only java.io.File type is supported. > > Maven currently u

Re: Mojo parameters of type java.nio.file.Path

Thanks for the answer. I meanwhile found https://github.com/eclipse/sisu.inject/commit/2676001d31a06fe94d2d9a167c5f078c2eba4f5a, but IMHO SISU 0.9.0-M1 is not used in any released Maven yet, so for the time being I am bound to using File parameters, right? Konrad On 2022/07/29 14:21:57 Romain

  1   2   >