Re: [DISCUSS] Support YAML poms

Looks good! Thanks a lot for sharing. I am wondering whether this should rather be based on SnakeYaml Engine (YAML 1.2 processor) instead of the legacy SnakeYaml (YAML 1.1). Also I am wondering if you disable deserialisation of potentially dangerous YAML (compare with https://en.wikipedia.org/wi

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 more release > w

Re: Leveraging SonarQube Cloud (fka SonarCloud)

On Sun, 5 Jan 2025 at 02:58, Gerd Aschemann wrote: >>> >>> >>> >>>> On 4. Jan 2025, at 22:28, Slawomir Jaranowski >>>> wrote: >>>> >>>> On Thu, 2 Jan 2025 at 14:10, Konrad Windszus wrote: >>>>> >>>

Re: Using git forks

Hi, There used to be some problems related to CI. At least ASF Jenkins differentiates between forked PRs and non-forked PRs. For GitHub Actions there is a difference with regards to permissions (https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/controlling-perm

Leveraging SonarQube Cloud (fka SonarCloud)

Hi, Maven currently does not leverage SonarQube analysis (nor any other static code analysis). Although onboarding currently requires one INFRA ticket per repo (https://cwiki.apache.org/confluence/pages/viewpage.action?spaceKey=INFRA&title=SonarCloud+for+ASF+projects) this is a one time action a

[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

Hi, Currently repository.apache.org is still a Nexus 2 repository. However Nexus 2 will be sunset in June 2025 (https://help.sonatype.com/en/sonatype-nexus-repository-2-sunsetting-information.html). Is the task to migrate to a Nexus 3 repository already captured so

[VOTE] Release Apache Maven Fluido Skin version 2.0.1

Hi, We solved 6 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317926&version=12355261&styleName=Text There are still a couple of issues left in JIRA. Staging repo: https://repository.apache.org/content/repositories/maven-2252/ https://repository.apache.org/content/re

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: > > Hi Benja

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, at

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

I cannot rebuild from the source-release.zip. When building with "mvn package" I get errors from spotless: [INFO] --- spotless:2.43.0:check (default) @ maven-fluido-skin --- [INFO] Index file does not exist. Fallback to an empty index [INFO] Sorting file /var/folders/f8/_3c0rvgd00n324sqjc8y_3wr00

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

Hi, The homebrew tap is still at 1.0.1 (https://github.com/mvndaemon/homebrew-mvnd/blob/master/Formula/mvnd%401.rb). I see that this does not belong to the ASF GitHub organisation, so do we consider this part of the Maven Daemon release process? It is documented as official way to install in h

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

and > https://maven.apache.org/shared/maven-filtering/ still shows 3.3.2. > > On Sun, Sep 8, 2024 at 11:36 AM Konrad Windszus wrote: >> >> Hi, >> >> The vote has passed with the following result: >> >> +1 : Michael, Olivier, Tamás, Sylwester >>

[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

Hi, Unlike plugin (with plugin management and its configuration) the reportSet (https://maven.apache.org/ref/3.9.9/maven-model/maven.html#class_reportSet) cannot be configured on a POM level which itself should not have the configured reports. Once a reportSuite is configured it is active both o

Disable ASF GitHub Bot comments in JIRA

Hi everyone, I consider the automatic JIRA comments being added for each GitHub PR comment quite verbose and redundant. Also the formatting is in some cases broken because it doesn’t properly escape for the Confluence markdown used by JIRA (e.g. look at https://issues.apache.org/jira/browse/MRE

[VOTE] Release Apache Maven Filtering 3.4.0

Hi, We solved 1 issue: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922&version=12354380&styleName=Text 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%20compon

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: > > Hi, >

Re: [DISCUSS] maven-core-plugin

> On 18. Aug 2024, at 12:59, Hervé Boutemy wrote: > > with Maven 4, we'll have to maintain a 4.x branch of each plugin in parallel > to the current Maven 3 compatible one: Maven 4 is the right time to have the > discussion and eventually change the structure > > we need to clarify what "cor

Maven Resolver inconsistency between VersionRangeResult and VersionResult

Hi, I am wondering why org.eclipse.aether.resolution.VersionResult[1] uses the type String for the resolved version while org.eclipse.aether.resolution.VersionRangeResult[2] uses type org.eclipse.aether.version.Version. This doesn’t seem very consistent. Is there a reason why it is not parsed fo

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

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 allowed consumers to deliberately use an old version of one plugin (e.g

Re: [VOTE] Release Maven Plugin Tools version 3.14.0

Hi, I would appreciate some cleanup of the branches after https://issues.apache.org/jira/browse/MPLUGIN-523. I see now 1) master 2) mvn4 3) maven-plugin-tools-3.7.x 4) maven-plugin-tools-3.x IIUC only 1 and 4 is relevant. Also in 1) I see a lot of code not relevant for v4 plugins like - http

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

Module is a quite overloaded term so you always have to specify the context. For me module without the prefix “Java” doesn’t implicitly mean Java module. Same would apply for “package”. Is it Java package or Maven package (the lifecycle phase)? Overall I don’t think it is worth the effort to do t

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

he/maven-gh-actions-shared/commit/994eebd0d7acb406c055aed405b32ca42415df91) >> With v4 it is working fine. >> Konrad >>> On 11. Aug 2024, at 11:00, Konrad Windszus wrote: >>> >>> >>> Hi, >>> By default our shared GH actions pipeline

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

024, at 11:00, Konrad Windszus wrote: > > > Hi, > By default our shared GH actions pipeline fails now for Java 8 on Mac OS: > > Run actions/setup-java@v4 > with: > java-version: 8 > distribution: temurin > cache: maven > java-package: jdk > check-lates

GH Action Shared v4 fails for Java 8 on Mac OS

Hi, By default our shared GH actions pipeline fails now for Java 8 on Mac OS: Run actions/setup-java@v4 with: java-version: 8 distribution: temurin cache: maven java-package: jdk check-latest: false server-id: github server-username: GITHUB_ACTOR server-password: GITHUB_TOKEN o

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

Hi Martin, First of all thanks a lot for the hard work. Much appreciated. However there is other compilers like the Groovy Eclipse Compiler (https://github.com/groovy/groovy-eclipse/blob/d6ac73c6ba4adadbd67c60bf130ad68f2284890f/extras/groovy-eclipse-compiler/src/main/java/org/codehaus/groovy/eclip

[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

Hi, I just executed "svn log https://svn.apache.org/repos/asf/maven/website/components/plugins/maven-war-plugin/index.html"; which exposes r1910420 | michaelo | 2023-06-15 09:06:23 +0200 (Do, 15 Jun 2023) | 1 line Publish

[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 casting this vote? > >

[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

Hi, I am wondering about the best practice to inject Sisu/JSR330 components into Mojos. We have two different possibilities: 1. Via annotation org.apache.maven.plugins.annotations.Component [1] which makes the referenced Sisu component also appear in the requirements section of the plugin des

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

Hi, There was a longer discussion in https://www.mail-archive.com/dev@maven.apache.org/msg132078.html (for some reason cannot find the thread in https://lists.apache.org/list.html?dev@maven.apache.org) and we kind of came to an agreement to reserve plugin major version 4 for plugins leveraging

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.apache.org/jira/projects/SCM/issues

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.apache.org/jira/issues/?jql=project%

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

> On Wed, Apr 10, 2024 at 1:09 PM Konrad Windszus wrote: > >> 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

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 2024, a

Revert commit 740dae43ca3ccf7692f37edf3184387e5666ca6b

Hi, I consider https://github.com/apache/maven/commit/740dae43ca3ccf7692f37edf3184387e5666ca6b wrong, as in fact the field requiredMavenVersion has been added quite recently and is only supported since Maven 4 (for details refer to https://issues.apache.org/jira/browse/MNG-7570). The referenced

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

HI, For me the site build of https://github.com/apache/jackrabbit-filevault-package-maven-plugin fails with Sitetools 2.0.0-M17 "[ERROR] Failed to execute goal org.apache.maven.plugins:maven-site-plugin:4.0.0-M14-SNAPSHOT:site (default-site) on project filevault-package-maven-plugin: Execution

Re: [DISCUSS] Maven Core Plugins versioning

This is slightly differently described on https://maven.apache.org/plugins/ Core pluginsPlugins corresponding to default core phases (ie. clean, compile). They may have multiple goals as well. But I think the intention is clear: This should apply to all plugins maintai

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 have no idea wh

Re: [DISCUSS] Maven Core Plugins versioning

Hi, I agree with both I. and II. Not sure I understand the need for III. IMHO breaking changes for users should almost never happen (or if at all only after a long deprecation phase) Maybe you can give an example you have in mind for III? But to make it visible to users I would say such an extrao

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 17 and hence require

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

Hi, According to https://maven.apache.org/pom/maven/#the-format-profile the git commits created through applying the spotless formatting should be ignored via a .git-blame-ignore-revs file. This file is automatically evaluated by GitHub blame view. This doesn’t work well if the formatting also

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

+1 The mentioned staging site https://maven.apache.org/doxia/doxia-archives/doxia-LATEST/ is not working though (returns a 404), but the HTML source in https://svn.apache.org/repos/asf/maven/doxia/website/components/doxia-archives/doxia-LATEST/index.html looks ok to me (svnpubsub set up correc

Re: Plugins documentations - improvements

Hi, currently those sections deviate slightly (e.g. the overview does not evaluate deprecation info) but we can probably consolidate overview and details into one section. Look at https://github.com/apache/maven-plugin-tools/blob/master/maven-plugin-report-plugin/src/main/java/org/apache/maven/p

MSKINS-229

gin forwarded message: > > From: Michael Osipov > Subject: Re: [VOTE] Release Apache Maven Reporting Exec version 2.0.0-M12 > Date: 26. November 2023 at 12:23:46 CET > To: dev@maven.apache.org > Reply-To: "Maven Developers List" > > Am 2023-11-26 um 11:35 schrieb Ko

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

For me the blocker for Maven Site 2.x final and related plugins is mostly https://issues.apache.org/jira/browse/MSKINS-229. IMHO this requires a fix in Doxia not in Fluido (because it has to work in a skin-agnostic way) but in the end what really matters is that the TOC macro works at all (at le

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, Hervé

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 that should be resolved

Re: [VOTE] Release Maven Plugin Tools version 3.10.1

Hi everyone, Sorry for the late response. Those changes were done deliberate due to what Michael said before. Should have mentioned that before. Does this require a dedicated JIRA with description or is it fine to improve the semantics like this silently (I fail to see any functional impact here

Using Sink API with XHTML markup

Hi, In the context of [1] I am working on using the Sink API to emit the goal documentation reports for Maven plugins. Currently there are XDoc documents emitted. Conversion is more or less straight-forward, but there is also input originally coming from javadoc which is already in XHTML format.

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

Hi, The error message is introduced with https://issues.apache.org/jira/browse/MSOURCES-121 in 3.3.0: If you have two goals both attaching an artifact with the same classifier and extension to the current project they will overwrite each other. Please check which classifiers are used for both goa

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 change to the ASF Maven voting

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 like to propose a chan

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

Hi, The initial goal of maven-shared-utils from https://maven.apache.org/shared/maven-shared-utils/ was never reached as plexus-utils was never decommissioned but rather received most attention in the past. Lots of new bugfixes only ended up in plexus-utils and were never backported to maven-s

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-alpha-2/apidocs/org

Re: Maven 3 API, backwards compatibility

On 2022/11/16 10:04:36 Tamás Cservenák wrote: ... > In general, I guess, we should. For this reason JapiCmp has been used in > Resolver since 1.9.0 (as noted on refd page end). I added https://issues.apache.org/jira/browse/MNG-7598 to track that. Currently we did a poor job when this was intend

Re: Maven 3 API, backwards compatibility

And done. > > Just as an example, here is what Maven Resolver has to say about same topic > (part of not-yet-released, vote is in process 1.9.1 version): > https://maven.apache.org/resolver-archives/resolver-LATEST/api-compatibility.html > > HTH > T > > On Wed, Nov 16, 202

Re: Maven 3 API, backwards compatibility

2022/11/16 09:20:11 Konrad Windszus wrote: > Hi, > Unfortunately Maven 3 didn’t define a proper API. In effect everything > somehow exposed through class loaders was considered API by plugin/extension > developers. > For Maven 4 a completely separate API was establi

Maven 3 API, backwards compatibility

Hi, Unfortunately Maven 3 didn’t define a proper API. In effect everything somehow exposed through class loaders was considered API by plugin/extension developers. For Maven 4 a completely separate API was established in package “org.apache.maven.api”, but what about the old packages used and exp

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 couple of issues left in JIRA

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't see it

Re: Improve connection between Maven and IDE?

> What will happen tomorrow, if Maven is approached by the NetBeans or IDEA > team with some text like > "What a nice tool you have here, it would be a shame to let something > happen to it, right? So, you should integrate this library to make it work > in our IDE...". plexus-build-utils is IDE

Re: Improve connection between Maven and IDE?

> behind is welcomed - but once again does not need any maven change. > > Le lun. 26 sept. 2022 à 19:23, Konrad Windszus a écrit : > > > Probably a misunderstanding then. It sounded a bit like you deny the > > benefit of having an API for incremental builds and IDE integra

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

Sorry for the copy&paste mistake above. The PR is at https://github.com/apache/jackrabbit-filevault-package-maven-plugin/pull/85. It failed after a simple upgrade as can be seen in https://ci-builds.apache.org/blue/organizations/jenkins/Jackrabbit%2Ffilevault-package-maven-plugin/detail/PR-85/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

I just tested this release with filevault-package-maven-plugin and run into the following exception (https://github.com/Netcentric/accesscontroltool/releases/tag/3.0.6): Caused by: org.apache.maven.plugin.PluginResolutionException: Plugin org.apache.jackrabbit:filevault-package-maven-plugin:1.

Re: Improve connection between Maven and IDE?

> I prefer to find a way not requiring to change any pojo which would be a > huge requirement and regression for no feature gain IMHO. I disagree here, actually better IDE integration is a big feature gain. Regarding the history of https://github.com/sonatype/sisu-build-api, this used to be c

Re: [VOTE] Release Apache Maven Daemon 0.8.1

th the > upgrade to GraalVM 2.22.0, the color output fix from @cstamas and the > additional tar.gz distributions that have been asked. > > Le lun. 19 sept. 2022 à 14:52, Konrad Windszus <mailto:k...@apache.org>> a écrit : > Hi Guillaume, > There is no Aarch64 support

Re: [VOTE] Release Apache Maven Daemon 0.8.1

t; Cheers, > Guillaume > > Le mar. 13 sept. 2022 à 10:34, Konrad Windszus a écrit : > 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

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

> On one hand, we all agree that .gitignore and .gitattributes (and so > on) are useful when building a project (prior to the final packaging). The primary purpose of those files are git commands. Having them evaluated by other tools is kind of unexpected (at least for me)... We already strip s

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

> I believe that all file files which are necessary for CI, SCM and others > are not required to be build in that build and are just noise. So I'd be > in favor of a PR for this. > > Michael Thanks for the comment. As such excludes are useful for all packaging plugins WDYT about maintaining su

ASF Source Assembly now contains .gitignore and .gitattributes

Hi, Due to the change https://github.com/codehaus-plexus/plexus-utils/commit/e8a8433894eae9e8f82cbba4b903508362e9322a all releases triggered with ASF Parent 27 contain a src.zip artifact which now also contain the previously exluded “.gitignore” and “.gitattributes” files. The descriptor definin

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 available at > > https://githu

Re: Replacements for ArtifactMetadataSource

I think you need to use MetadataResolver (similar to what is done in https://github.com/apache/maven/blob/a53a1aa232bc383baf055d884a7c66319d10d404/maven-resolver-provider/src/main/java/org/apache/maven/repository/internal/DefaultVersionRangeResolver.java#L140) although https://github.com/apache/

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

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.html 2. https://maven.apache.org/ref/3.8.6/apidocs/org/apache/maven/bridge/MavenRepositorySystem.html 3. https://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

e same custom alignment for Path we just need to copy this > class and replace 'File' with 'Path': > > https://github.com/eclipse/sisu.plexus/blob/releases/0.3.5/org.eclipse.sisu.plexus/src/org/codehaus/plexus/component/configurator/converters/basic/FileConverter.java >

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

tps://rmannibucau.metawerx.net/> | Old Blog > > <http://rmannibucau.wordpress.com> | Github < > > https://github.com/rmannibucau> | > > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book > > < > > https://www.packtpub.com/application-developmen

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

oracle.com/javase/7/docs/api/java/io/File.html#toPath()> > > On Fri, Jul 29, 2022 at 4:06 PM Konrad Windszus wrote: > > > > Hi, > > According to > https://maven.apache.org/guides/plugin/guide-java-plugin-development.html#files-and-directories > only java.io.File

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

<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book > <https://www.packtpub.com/application-development/java-ee-8-high-performance> > > > Le ven. 29 juil. 2022 à 16:06, K

  1   2   >