Re: [VOTE] Release Maven Resolver 1.9.4
+1 Le ven. 13 janv. 2023 à 08:11, Tamás Cservenák a écrit : > Howdy, > > We solved 5 issues: > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRESOLVER%20AND%20fixVersion%20%3D%201.9.4 > > There are still some issues in JIRA: > https://issues.apache.org/jira/projects/MRESOLVER/issues > > Staging repository: > https://repository.apache.org/content/repositories/maven-1851 > > Source release SHA512: > > e02988b875a55db1f1eb0976a06d7222cb1598228634735a9afdd27b827d48ae1c37629311613949f67b171bc9feb611f5cbdfe875003326144b20c1d2539ca3 > > Staging site: > https://maven.apache.org/resolver-archives/resolver-LATEST/ > > Guide to testing staged releases: > https://maven.apache.org/guides/development/guide-testing-releases.html > > Vote open for at least 72 hours. > > [ ] +1 > [ ] +0 > [ ] -1 > -- Guillaume Nodet
[VOTE] Release Maven Plugin Tools 3.7.1
Howdy, We solved 1 issue https://issues.apache.org/jira/issues/?jql=project%20%3D%20MPLUGIN%20AND%20fixVersion%20%3D%203.7.1 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%20MPLUGIN%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20key Staging repo: https://repository.apache.org/content/repositories/maven-1852/ Source release SHA512: a4d16ed3f9618990f5327eb8bb1a137c3effaa1f90651925c75ff6df1a16c7bb52de1facb5b90ce4a7ca5714f1b35a28da92de98e7678d55ad9e9ca3246e61bb Staging site: https://maven.apache.org/plugin-tools-archives/plugin-tools-LATEST/ Guide to testing staged releases: https://maven.apache.org/guides/development/guide-testing-releases.html Vote open for at least 72 hours. [ ] +1 [ ] +0 [ ] -1
[VOTE] Release Maven Resolver 1.9.4
Howdy, We solved 5 issues: https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRESOLVER%20AND%20fixVersion%20%3D%201.9.4 There are still some issues in JIRA: https://issues.apache.org/jira/projects/MRESOLVER/issues Staging repository: https://repository.apache.org/content/repositories/maven-1851 Source release SHA512: e02988b875a55db1f1eb0976a06d7222cb1598228634735a9afdd27b827d48ae1c37629311613949f67b171bc9feb611f5cbdfe875003326144b20c1d2539ca3 Staging site: https://maven.apache.org/resolver-archives/resolver-LATEST/ Guide to testing staged releases: https://maven.apache.org/guides/development/guide-testing-releases.html Vote open for at least 72 hours. [ ] +1 [ ] +0 [ ] -1
Re: Maven 3 API, backwards compatibility
Hi, after following the discussion, i still have no idea how to maintain a core-extension that needs to run on both maven 3 and 4. Could anyone plz give some suggestions? On Fri, Nov 18, 2022 at 4:20 PM Guillaume Nodet wrote: > Le mer. 16 nov. 2022, 10:20, Konrad Windszus a écrit : > > > 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 exported > > in Maven 3? > > > > For example in the context of > > https://issues.apache.org/jira/browse/MNG-7588 < > > https://issues.apache.org/jira/browse/MNG-7588> I want to evolve the > > package “org.apache.maven.plugin.descriptor”. > > We already figured out that this particular package (although not part of > > the Maven 4 API) is used from both Maven Core as well as Maven Plugin > > Tools, therefore this probably needs to stay backwards compatible. > > What about others like > > > https://github.com/apache/maven/blob/master/maven-core/src/main/java/org/apache/maven/plugin/MavenPluginManager.java > ? > > < > > > https://github.com/apache/maven/blob/master/maven-core/src/main/java/org/apache/maven/plugin/MavenPluginManager.java > > ?> > > This interface should IMHO never been implemented outside Maven Core but > > in fact it was exposed to all plugins/extensions (via > > > https://github.com/apache/maven/blob/a6b1ebb1cd40ca4b288fdeb30c6d2460323aa25b/maven-core/src/main/resources/META-INF/maven/extension.xml#L40 > > < > > > https://github.com/apache/maven/blob/a6b1ebb1cd40ca4b288fdeb30c6d2460323aa25b/maven-core/src/main/resources/META-INF/maven/extension.xml#L40 > > >). > > > > There are three options coming to my mind: > > > > 1. Deprecate the interfaces we don’t consider API and create new ones for > > Maven 4 which are not exported! > > > > I think that's the way to go. > We'd also need to deprecate a bunch of jars and in maven-shared like > m-artifact-transfer, maven-dependency-tree etc... > One of the goal is also to completely hide the resolver. > > 2. Modify the existing interfaces in a backwards compatible way (but > > somehow add a marker that they should not be implemented outside core) > > > > > > 3. Modify the existing interfaces in a backwards compatible way (but > > somehow add a marker that they should not be implemented outside core) > > > > For all three options we somehow need to come up with a list of > > classes/interfaces currently being exported through the API class loader, > > which should be considered private and agree on an Annotation/Javadoc for > > that (something like > > > https://github.com/mulesoft/api-annotations/blob/40b258afeff6560241dee5001ed00f1deb392e47/src/main/java/org/mule/api/annotation/NoImplement.java#L29 > > < > > > https://github.com/mulesoft/api-annotations/blob/40b258afeff6560241dee5001ed00f1deb392e47/src/main/java/org/mule/api/annotation/NoImplement.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 > > > > >
[VOTE] Release Maven Fluido Skin version 2.0.0-M2
Hi, We solved 10 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317926=12352732 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSKINS%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20%22Fluido%20Skin%22 Staging repo: https://repository.apache.org/content/repositories/maven-1850/ https://repository.apache.org/content/repositories/maven-1850/org/apache/maven/skins/maven-fluido-skin/2.0.0-M2/maven-fluido-skin-2.0.0-M2-source-release.zip Source release checksum(s): maven-fluido-skin-2.0.0-M2-source-release.zip sha512: ad6bf1ee15c4b959518025090853a36d1294913529839bd7c84a798cb7278c245b70e186b6fd60e53a35710a034b492044d899e5c0290d4a12514dcc3e9ff049 Staging site: https://maven.apache.org/components/skins-archives/maven-fluido-skin-LATEST/ Guide to testing staged releases: https://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [RESULT] [VOTE] Release Maven Surefire version 3.0.0-M8
Am 2023-01-12 um 02:23 schrieb Nick Stolwijk: Hi Michael, Thanks for the release! A little side note for next time, the link in the announcement mail is not working. It should be https://maven.apache.org/surefire/ instead of https://maven.apache.org/maven-surefire/. Thanks, fixed my docs - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [RESULT] [VOTE] Release Maven Surefire version 3.0.0-M8
For reference: This is the issue https://issues.apache.org/jira/browse/SUREFIRE-2141 The problem is about the compatibility of a third party library used in the tests, that doesn't work on ARM platforms There is no quick fix Enrico Il giorno gio 12 gen 2023 alle ore 02:24 Nick Stolwijk ha scritto: > > Hi Michael, > > Thanks for the release! A little side note for next time, the link in the > announcement mail is not working. It should be > https://maven.apache.org/surefire/ instead of > https://maven.apache.org/maven-surefire/. > > With regards, > > Nick Stolwijk > > ~~~ Try to leave this world a little better than you found it and, when > your turn comes to die, you can die happy in feeling that at any rate you > have not wasted your time but have done your best ~~~ > > Lord Baden-Powell > > > On Wed, 11 Jan 2023 at 22:24, Michael Osipov wrote: > > > Hi, > > > > The vote has passed with the following result: > > > > +1: Herve Boutemy, Slawomir Jaranowski, Romain Manni-Bucau, Karl Heinz > > Marbaise, Petr Široký > > > > PMC quorum: reached > > > > I will promote the artifacts to the central repo, the source release ZIP > > file > > and add this release the board report. > > - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Doxia 1.12.0 and Doxia Converter 1.3
+1 On Mon, Jan 9, 2023 at 10:47 PM Hervé Boutemy wrote: > Hi, > > I'd like to release Doxia 1.12.0 and Doxia Converter 1.3 > The main goal is to support Markdown output. > > Doxia 1.12.0 release notes > https://issues.apache.org/jira/projects/DOXIA/versions/12351764 > > Staged repo: > https://repository.apache.org/content/repositories/maven-1848/ > sources: > https://repository.apache.org/content/repositories/maven-1848/org/apache/maven/doxia/doxia/1.12.0/doxia-1.12.0-source-release.zip > sources sha512: > 14b27a8074aa77635fda38fbd419c5757d5578978b67f3d02997419e53b73148fd080fa7b25957c74906608219bf8f887c9e832f86c75b9eae9e575d3160% > > staged site: https://maven.apache.org/doxia/doxia-archives/doxia-LATEST/ > > Doxia Converter 1.3 release notes > https://issues.apache.org/jira/projects/DOXIATOOLS/versions/12330662 > > staged repo: > https://repository.apache.org/content/repositories/maven-1849/ > sources: > https://repository.apache.org/content/repositories/maven-1849/org/apache/maven/doxia/doxia-converter/1.3/doxia-converter-1.3-source-release.zip > sources sha512: > fd82c96acd5bd8bc2dd84127d1c2143df57166f04bf0ac47f5d1b99728fe701126be4f1304388f6003fe81970bb4a9591f22b55eeece5023750d511d5b007aaf% > > vote open for 72H > +1 > 0 > -1 > > Regards, > > Hervé > > > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
