Re: [DISCUSS] checking reproducible builds

As creating a new maven-artifact-plugin will probably take some time, maybe it would be possible to push a release build of https://github.com/apache/maven-studies/tree/maven-buildinfo-plugin to Maven Central. Or is there already a rough schedule for coming up with the new

Re: New release of ASF Parent pom.xml

t; > > everything seems ok now > > https://maven.apache.org/pom-archives/asf-LATEST/ > > > > if nobody objects, I'll start the release process this WE > > > > Regards, > > > > Hervé > > > > Le mardi 8 juin 2021, 09:52:32 CEST Konrad Windszus a écri

New release of ASF Parent pom.xml

Hi, the last release of ASF Parent 23 is now more than 1.5 years old. Lots of plugins have received updates and quite some features have been added. Would it be possible to review the open PRs and spin a release soon? Thanks in advance, Konrad

Re: New release of ASF Parent pom.xml

f nobody objects, I'll start the release process this WE > > Regards, > > Hervé > > Le mardi 8 juin 2021, 09:52:32 CEST Konrad Windszus a écrit : > > Hi, > > the last release of ASF Parent 23 is now more than 1.5 years old. Lots of > > plugins have received

Re: [maven-gpg-plugin] Unable to sign artifacts with SHA-256 or higher

Look at https://issues.apache.org/jira/browse/MPOM-244 which should solve this for ASF projects. Konrad > On 27. May 2021, at 13:29, Janardhan wrote: > > Thank you, for the generous response. > > The file hashes are created by maven-resolver,

Re: New release of ASF Parent pom.xml

e samedi 12 juin 2021, 17:15:00 CEST Hervé BOUTEMY a écrit : > > done > > > > Le vendredi 11 juin 2021, 10:14:09 CEST Konrad Windszus a écrit : > > > Great thanks, the documentation still needs some update. It says in > > > https://maven.apache.org/pom-archives/a

Re: Maven artifacts SHA256 | SHA512 checksums

Hi Petr, this should be feasible with checksum-maven-plugin in the upcoming version (https://issues.apache.org/jira/browse/MPOM-244?focusedCommentId=17255937=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17255937). Konrad

Re: [VOTE] Release Apache Maven Artifact Plugin version 3.0.0

I tried to run on several projects. Looks good to me. Thanks for pushing it. +1 (non-binding) Konrad - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org

Re: [VOTE] Release Maven Plugin Tools version 3.6.3

I agree here, it seems unlikely that Sonatype is releasing a fix for it soon, and given that OSSRH documentation recommends leveraging the staging-maven-plugin in https://central.sonatype.org/publish/publish-maven/#distribution-management-and-authentication I would assume a lot of open source

Re: [VOTE] Release Maven Plugin Tools version 3.6.4

+1 (non-binding). Thanks a lot for driving this release. With enough PMC votes and the waiting time being over can you close this and publish the artifacts? Thanks Konrad On 2022/01/10 23:35:03 Slawomir Jaranowski wrote: > Hi, > > We solved 5 issues: >

Re: [VOTE] Release Apache Maven version 3.8.5

Probably related to https://github.com/apache/maven/commit/572d5260b9040bd063b3dc84ce51684b8379df10 which increased the maven-compiler-plugin to 3.10.0 including https://issues.apache.org/jira/browse/MCOMPILER-205. Not sure why they are not available in the reference build though... Konrad

Re: [DISCUSS] New Maven Core API for 4.x

/spotbugs/spotbugs/blob/51e586bed98393e53559a38c1f9bd15f54514efa/spotbugs/src/main/java/edu/umd/cs/findbugs/ba/NullnessAnnotation.java#L35. Not sure where the related matching algorithm is in the SonarQube source code Konrad On 2022/03/18 11:00:29 Konrad Windszus wrote: > Hi, > this looks

Re: [DISCUSS] New Maven Core API for 4.x

Hi, this looks really nice. Just one observation: I would recommend to get rid of JSR 305 null-annotations due to it being dormant and having split-package issues (https://nipafx.dev/jsr-305-java-9/). Consider migrating to either spotbugs

Re: Release of maven-verifier

jectId=12317922=12351428 > > I'm going to release 1.8.0 at the weekend (19-20 of March) > > Does anybody else want to add something more? > > > wt., 8 mar 2022 o 08:26 Konrad Windszus napisał(a): > > > Hi, > > I would really appreciate if some committers

Release of maven-verifier

Hi, I would really appreciate if some committers could look at the following three PRs for maven-verifier https://github.com/apache/maven-verifier/pull/4 https://github.com/apache/maven-verifier/pull/6

Release of m-plugin-p 3.6.3

Hi, as m-plugin-p 3.6.2 contained several regressions which are meanwhile all fixed (https://issues.apache.org/jira/projects/MPLUGIN/versions/12351104 ) it would be great to have a release 3.6.3 soon. Is there anything still

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: [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

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

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

Re: maven-shared-utils what the future is ...

to plexus-utils... does this depend on jansi > or something? > I'd rather create a new module (if broadly used, many dependents) or fit > it somewhere else... > > Where is this currently used? > > T > > On Sun, Jun 26, 2022 at 6:53 PM Konrad Windszus wrote: > >

JSR330: Overriding the default lifecycle

Hi, What is the best way to get rid of plexus metadata (components.xml) and override the default lifecycle mapping for a certain type (as outlined in https://blog.sonatype.com/2009/08/create-a-customized-build-process-in-maven/) only leveraging JSR 330 annotations

Re: JSR330: Overriding the default lifecycle

oviders > > Le lundi 4 juillet 2022, 08:48:01 CEST Konrad Windszus a écrit : > > Hi, > > What is the best way to get rid of plexus metadata (components.xml) and > > override the default lifecycle mapping for a certain type (as outlined in > > https://blog.sonatype.

Re: maven-shared-utils what the future is ...

Sorry to reuse this thread, but another package which is not provided by another library/artifact yet is https://maven.apache.org/shared/maven-shared-utils/apidocs/org/apache/maven/shared/utils/logging/package-summary.html. I would like to get rid of the maven-shared-utils dependency. Would you

Re: [VOTE] Release Apache Maven Fluido Skin version 1.11.1

+1 (non-binding) Tested with https://jackrabbit.apache.org/filevault/index.html. Thanks for doing the release. Konrad - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail:

Re: JSR330: Overriding the default lifecycle

On 2022/07/06 14:18:28 Tamás Cservenák wrote: > Maven 3.0 did not support sisu-index (produced by sisu-maven-plugin during > build), but 3.1 onward does support it. > > Hence. If you support Maven 3.0 inclusive, you must stick with plexus xml, > otherwise is not required. > > T The problem

Re: JSR330: Overriding the default lifecycle

> or are you trying to create bindings for a new packaging? Yes, this is what I am doing. You can see it already in https://github.com/apache/jackrabbit-filevault-package-maven-plugin/blob/master/src/main/resources/META-INF/plexus/components.xml. But from all your information I derived that I

Re: JSR330: Overriding the default lifecycle

in the effective pom.xml). Only for other plugins it is best practice to always set versions (otherwise Maven would check the remote repo for the latest version and in general builds are far less reproducible). Thanks again for all the helpful input. Konrad On 2022/07/14 08:26:59 Konrad Windszus wrote: >

Mojo parameters of type java.nio.file.Path

Hi, According to https://maven.apache.org/guides/plugin/guide-java-plugin-development.html#files-and-directories only java.io.File type parameters are supported for dealing with file paths. I was assuming that every complex type is supported which has a constructor taking a single String value

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

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

se/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 type parameters

Re: JSR330: Overriding the default lifecycle

997 > > HTH > T > > On Wed, Jul 6, 2022 at 4:26 PM Konrad Windszus wrote: > > > > > > > On 2022/07/06 14:18:28 Tamás Cservenák wrote: > > > Maven 3.0 did not support sisu-index (produced by sisu-maven-plugin > > during > > > build), but

Re: JSR330: Overriding the default lifecycle

the difference comes from? Thanks, Konrad On 2022/07/14 07:10:08 Konrad Windszus wrote: > Hi Tamás, > thanks a lot for that example. Unfortunately one cannot use > `o.a.m.lifecycle.mapping.Lifecycle.setPhases(Map)` due to > https://issues.apache.org/jira/browse/MNG-5958 in Maven

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

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

Re: Improve connection between Maven and IDE?

ehind 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 integrati

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: [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: [VOTE] Release Apache Maven Daemon 0.8.1

eers, > 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 candidate

Re: [VOTE] Release Apache Maven Daemon 0.8.1

e > 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 in

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

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

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

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

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

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

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

Sorry for the copy 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

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.

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

s://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-development/jav

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

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

lignment 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 > > > On Sun, 31 Jul 2

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

Re: Maven 3 API, backwards compatibility

> > 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, 2022 at 10:26

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

Re: Maven 3 API, backwards compatibility

On 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

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? > >

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=12344367 > > There are still a couple of issues left in JIRA: >

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

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

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

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

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

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

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

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

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

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: 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] 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: [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

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

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

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:

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 > > "[

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

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,

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

gt; > 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: [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=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=12354136 > > There are still a couple of issues left in JIRA: >

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