Re: [VOTE] Release Maven Javadoc Plugin version 3.3.2
+1 Reproducible Build ok: reference done with JDK 8 on Windows Regards, Hervé Le lundi 7 février 2022, 22:12:26 CET Michael Osipov a écrit : > Hi, > > We solved 3 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317529 > rsion=12350586 > > There are still a couple of issues left in JIRA: > https://issues.apache.org/jira/projects/MJAVADOC/issues > > Staging repo: > https://repository.apache.org/content/repositories/maven-1707/ > https://repository.apache.org/content/repositories/maven-1707/org/apache/mav > en/plugins/maven-javadoc-plugin/3.3.2/maven-javadoc-plugin-3.3.2-source-rele > ase.zip > > Source release checksum(s): > maven-javadoc-plugin-3.3.2-source-release.zip > sha512: > 9fccfb11919f50615c91b699cef0edf241eae9f956be4cb2ebb67855823473c3e4ba5acd6b14 > 19dcf274ec72ee202e2b534a1c9a5c471f2e4dd0a598b46fc232 > > Staging site: > https://maven.apache.org/plugins-archives/maven-javadoc-plugin-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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: POC using release-drafter for github release
On Thu, 10 Feb 2022 at 02:04, Tamás Cservenák wrote: > Howdy, > > Yes, looks good, but one thing bothers me: > Does this mean that Maven projects -- if release-drafter is to be used -- > will have their release notes stored and accessible in their mirror > repositories only? > I do not see this as a mandatory part of the release process but a nice feature to add. (it's 98,7802% automatic so do not need much extra work) And especially for plugins because these days a lot of people use github and dependabot. So they receive such dependabot PR to update a maven plugin [1]. Reading this it's hard to figure out what has changed and why it's broken now with this upgrade (if you are lucky to know it's broken because you have configured some checks with some CI tooling). Then you google maven-compiler 3.9.0 and you find a link to a mailing list archive entry [2] well at this stage it is not too bad you found some official email from Apache Maven folks and you have a link to https://maven.apache.org/plugins/maven-compiler-plugin/ Where are there any details on the last release? (I'm not pointing anybody as I'm definitely guilty as well regarding the lack of documentation :) ) At this stage ok let's look at the email content. Oh there are some cryptic `[MCOMPILER-359]` (yup it's text email so no links) Not sure most of the users know what to do with that. I know `google it` :) but still takes more time than a click Anyway I wouldn't make it mandatory especially for some "obscure" shared components only used by our plugins. but anyway if any volunteers for that why not. /Olivier [1] https://github.com/cometd/cometd/pull/1125 [2] https://lists.apache.org/thread/9j2yf1771qwkhcrgpc22nf5gqffxq8cf > > T > > On Wed, Feb 9, 2022 at 4:57 PM Slawomir Jaranowski > > wrote: > > > Looks great. > > > > To avoid all PR in the first release we can add an empty release note for > > the latest release tag and then the new release draft should contains > only > > PR from the latest release not all. > > > > śr., 9 lut 2022 o 05:10 Olivier Lamy napisał(a): > > > > > Hi > > > Github has a feature to attach a release note to tag/release. > > > The content is then used when dependabot generates his famous PR all > > > over the world!! (yup a maven plugin generates a lot!!) > > > Our current content is not very user friendly > > > > > > While preparing the maven-compiler-plugin new release I have made some > > > tests using release-drafter tool [1]. > > > This generates the content here: > > > https://github.com/apache/maven-compiler-plugin/releases > > > The release notes will automatically contains only content from PRs (PR > > > must have a label to appear in a dedicated section otherwise they will > be > > > in the top, see mapping label/section here [2]) > > > This mapping is a default which can be shared between all project so > the > > > configuration is very simple see [3]. > > > Please note the first time it's used the first release will > > > contain everything (all PRs) from the start as there is no first > release. > > > The process is manual at the end, after all of our release process > steps, > > > you just need to go to GH ui then publish the release (manual. > > > modifications still possible). > > > > > > comments? thoughts? complaints :)? > > > > > > cheers > > > Olivier > > > > > > PS: if you want to use this be sure to modify manually the content > before > > > the publish as the content is regenerated for every merge PR > > > > > > [1] https://github.com/release-drafter/release-drafter > > > [2] > > > > > > > > > https://github.com/apache/maven-gh-actions-shared/blob/main/.github/release-drafter.yml > > > [3] > > > > > > > > > https://github.com/apache/maven-compiler-plugin/blob/master/.github/release-drafter.yml > > > and > > > > > > > > > https://github.com/apache/maven-compiler-plugin/blob/master/.github/workflows/release-drafter.yml > > > > > > > > > -- > > Sławomir Jaranowski > > >
Re: Upcoming release of maven-dependency-plugin
Hi Slawomir, a few weeks ago I started working on extending the "properties" goal to create a version property per dependency. This would be very useful for projects like Quarkus that have a big BOM and would like to reuse versions from that BOM for various things in integration tests etc. It would be nice to have more time to finish that, but I wouldn't call this "critical". Cheers, Falko Am 09.02.2022 um 23:50 schrieb Slawomir Jaranowski: Hi, There are 17 issues resolved https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317227=12340588 Some of them are critical. Do we have plans to resolve more issues in the near future? Last release was about 7 months ago. If there are no objections I can take care of it next week. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Upcoming release of maven-dependency-plugin
Hi, There are 17 issues resolved https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317227=12340588 Some of them are critical. Do we have plans to resolve more issues in the near future? Last release was about 7 months ago. If there are no objections I can take care of it next week. -- Sławomir Jaranowski
[ANN] Apache Maven Reporting Impl version 3.1.0 released
The Apache Maven team is pleased to announce the release of the Maven Reporting Impl version 3.1.0. https://maven.apache.org/shared/maven-reporting-impl/ Release Notes - Maven Shared Components - Version maven-reporting-impl-3.1.0 ** Improvement * [MSHARED-813] - Require Java 7 * [MSHARED-879] - make build Reproducible ** Dependency upgrade * [MSHARED-956] - Set minimum supported Maven version to 3.1.0 * [MSHARED-1027] - Update Doxia to 1.11.1 and Doxia Sitetools to 1.11.1 * [MSHARED-1028] - Upgrade Maven Reporting API to 3.1.0 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[RESULT] [VOTE] Release Apache Maven Reporting Impl version 3.1.0
Hi, The vote has passed with the following result: +1: Michael Osipov, Tibor Digana, Olivier Lamy, Hervé Boutemy, Tamás Cservenák 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] Release Maven Javadoc Plugin version 3.3.2
Am 2022-02-07 um 22:12 schrieb Michael Osipov: Hi, We solved 3 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317529=12350586 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/projects/MJAVADOC/issues Staging repo: https://repository.apache.org/content/repositories/maven-1707/ https://repository.apache.org/content/repositories/maven-1707/org/apache/maven/plugins/maven-javadoc-plugin/3.3.2/maven-javadoc-plugin-3.3.2-source-release.zip Source release checksum(s): maven-javadoc-plugin-3.3.2-source-release.zip sha512: 9fccfb11919f50615c91b699cef0edf241eae9f956be4cb2ebb67855823473c3e4ba5acd6b1419dcf274ec72ee202e2b534a1c9a5c471f2e4dd0a598b46fc232 Staging site: https://maven.apache.org/plugins-archives/maven-javadoc-plugin-LATEST/ Guide to testing staged releases: https://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. +1 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: POC using release-drafter for github release
Hello everyone, For what’s worth JReleaser supports a similar set of features for creating a changelog based on Git history. For the time being JReleaser categorizes commit messages following your own conventions. The rules are inspired by release-drafter. The pros are: - set up your own conventions - generated changelog can be stored anywhere, not just at the GH mirror - may be used via jreleaser-maven-plugin - works locally and on CI - can post releases as drafts to allow manual edits - can use templates to tweak parts or the whole changelog - initial tag/release is configurable. Matter of fact may be uses to retroactively generate Git releases + changelog on projects that only have tags - works with any Git service as it only requires reading local commit information The cons are: - does not read issue/PR labels to categorize commits. This feature may be added in the future - some features require a local GH token for read access (when resolving username/emails from GH) A PR is currently underway at the mvnd project to test it out https://github.com/apache/maven-mvnd/pull/574 Disclaimer: I’m the author of JReleaser. Cheers Andres Sent from my primitive tricorder > On 9 Feb 2022, at 17:04, Tamás Cservenák wrote: > > Howdy, > > Yes, looks good, but one thing bothers me: > Does this mean that Maven projects -- if release-drafter is to be used -- > will have their release notes stored and accessible in their mirror > repositories only? > > T > >> On Wed, Feb 9, 2022 at 4:57 PM Slawomir Jaranowski >> wrote: >> >> Looks great. >> >> To avoid all PR in the first release we can add an empty release note for >> the latest release tag and then the new release draft should contains only >> PR from the latest release not all. >> >> śr., 9 lut 2022 o 05:10 Olivier Lamy napisał(a): >> >>> Hi >>> Github has a feature to attach a release note to tag/release. >>> The content is then used when dependabot generates his famous PR all >>> over the world!! (yup a maven plugin generates a lot!!) >>> Our current content is not very user friendly >>> >>> While preparing the maven-compiler-plugin new release I have made some >>> tests using release-drafter tool [1]. >>> This generates the content here: >>> https://github.com/apache/maven-compiler-plugin/releases >>> The release notes will automatically contains only content from PRs (PR >>> must have a label to appear in a dedicated section otherwise they will be >>> in the top, see mapping label/section here [2]) >>> This mapping is a default which can be shared between all project so the >>> configuration is very simple see [3]. >>> Please note the first time it's used the first release will >>> contain everything (all PRs) from the start as there is no first release. >>> The process is manual at the end, after all of our release process steps, >>> you just need to go to GH ui then publish the release (manual. >>> modifications still possible). >>> >>> comments? thoughts? complaints :)? >>> >>> cheers >>> Olivier >>> >>> PS: if you want to use this be sure to modify manually the content before >>> the publish as the content is regenerated for every merge PR >>> >>> [1] https://github.com/release-drafter/release-drafter >>> [2] >>> >>> >> https://github.com/apache/maven-gh-actions-shared/blob/main/.github/release-drafter.yml >>> [3] >>> >>> >> https://github.com/apache/maven-compiler-plugin/blob/master/.github/release-drafter.yml >>> and >>> >>> >> https://github.com/apache/maven-compiler-plugin/blob/master/.github/workflows/release-drafter.yml >>> >> >> >> -- >> Sławomir Jaranowski >>
Re: POC using release-drafter for github release
Howdy, Yes, looks good, but one thing bothers me: Does this mean that Maven projects -- if release-drafter is to be used -- will have their release notes stored and accessible in their mirror repositories only? T On Wed, Feb 9, 2022 at 4:57 PM Slawomir Jaranowski wrote: > Looks great. > > To avoid all PR in the first release we can add an empty release note for > the latest release tag and then the new release draft should contains only > PR from the latest release not all. > > śr., 9 lut 2022 o 05:10 Olivier Lamy napisał(a): > > > Hi > > Github has a feature to attach a release note to tag/release. > > The content is then used when dependabot generates his famous PR all > > over the world!! (yup a maven plugin generates a lot!!) > > Our current content is not very user friendly > > > > While preparing the maven-compiler-plugin new release I have made some > > tests using release-drafter tool [1]. > > This generates the content here: > > https://github.com/apache/maven-compiler-plugin/releases > > The release notes will automatically contains only content from PRs (PR > > must have a label to appear in a dedicated section otherwise they will be > > in the top, see mapping label/section here [2]) > > This mapping is a default which can be shared between all project so the > > configuration is very simple see [3]. > > Please note the first time it's used the first release will > > contain everything (all PRs) from the start as there is no first release. > > The process is manual at the end, after all of our release process steps, > > you just need to go to GH ui then publish the release (manual. > > modifications still possible). > > > > comments? thoughts? complaints :)? > > > > cheers > > Olivier > > > > PS: if you want to use this be sure to modify manually the content before > > the publish as the content is regenerated for every merge PR > > > > [1] https://github.com/release-drafter/release-drafter > > [2] > > > > > https://github.com/apache/maven-gh-actions-shared/blob/main/.github/release-drafter.yml > > [3] > > > > > https://github.com/apache/maven-compiler-plugin/blob/master/.github/release-drafter.yml > > and > > > > > https://github.com/apache/maven-compiler-plugin/blob/master/.github/workflows/release-drafter.yml > > > > > -- > Sławomir Jaranowski >
Re: POC using release-drafter for github release
Looks great. To avoid all PR in the first release we can add an empty release note for the latest release tag and then the new release draft should contains only PR from the latest release not all. śr., 9 lut 2022 o 05:10 Olivier Lamy napisał(a): > Hi > Github has a feature to attach a release note to tag/release. > The content is then used when dependabot generates his famous PR all > over the world!! (yup a maven plugin generates a lot!!) > Our current content is not very user friendly > > While preparing the maven-compiler-plugin new release I have made some > tests using release-drafter tool [1]. > This generates the content here: > https://github.com/apache/maven-compiler-plugin/releases > The release notes will automatically contains only content from PRs (PR > must have a label to appear in a dedicated section otherwise they will be > in the top, see mapping label/section here [2]) > This mapping is a default which can be shared between all project so the > configuration is very simple see [3]. > Please note the first time it's used the first release will > contain everything (all PRs) from the start as there is no first release. > The process is manual at the end, after all of our release process steps, > you just need to go to GH ui then publish the release (manual. > modifications still possible). > > comments? thoughts? complaints :)? > > cheers > Olivier > > PS: if you want to use this be sure to modify manually the content before > the publish as the content is regenerated for every merge PR > > [1] https://github.com/release-drafter/release-drafter > [2] > > https://github.com/apache/maven-gh-actions-shared/blob/main/.github/release-drafter.yml > [3] > > https://github.com/apache/maven-compiler-plugin/blob/master/.github/release-drafter.yml > and > > https://github.com/apache/maven-compiler-plugin/blob/master/.github/workflows/release-drafter.yml > -- Sławomir Jaranowski
Re: [VOTE] Release Maven Javadoc Plugin version 3.3.2
+1 śr., 9 lut 2022, 11:14 użytkownik Olivier Lamy napisał: > +1 > > On Tue, 8 Feb 2022 at 07:12, Michael Osipov wrote: > > > Hi, > > > > We solved 3 issues: > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317529=12350586 > > > > There are still a couple of issues left in JIRA: > > https://issues.apache.org/jira/projects/MJAVADOC/issues > > > > Staging repo: > > https://repository.apache.org/content/repositories/maven-1707/ > > > > > https://repository.apache.org/content/repositories/maven-1707/org/apache/maven/plugins/maven-javadoc-plugin/3.3.2/maven-javadoc-plugin-3.3.2-source-release.zip > > > > Source release checksum(s): > > maven-javadoc-plugin-3.3.2-source-release.zip > > sha512: > > > > > 9fccfb11919f50615c91b699cef0edf241eae9f956be4cb2ebb67855823473c3e4ba5acd6b1419dcf274ec72ee202e2b534a1c9a5c471f2e4dd0a598b46fc232 > > > > Staging site: > > https://maven.apache.org/plugins-archives/maven-javadoc-plugin-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: [VOTE] Release Maven Javadoc Plugin version 3.3.2
+1 On Tue, 8 Feb 2022 at 07:12, Michael Osipov wrote: > Hi, > > We solved 3 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317529=12350586 > > There are still a couple of issues left in JIRA: > https://issues.apache.org/jira/projects/MJAVADOC/issues > > Staging repo: > https://repository.apache.org/content/repositories/maven-1707/ > > https://repository.apache.org/content/repositories/maven-1707/org/apache/maven/plugins/maven-javadoc-plugin/3.3.2/maven-javadoc-plugin-3.3.2-source-release.zip > > Source release checksum(s): > maven-javadoc-plugin-3.3.2-source-release.zip > sha512: > > 9fccfb11919f50615c91b699cef0edf241eae9f956be4cb2ebb67855823473c3e4ba5acd6b1419dcf274ec72ee202e2b534a1c9a5c471f2e4dd0a598b46fc232 > > Staging site: > https://maven.apache.org/plugins-archives/maven-javadoc-plugin-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: [VOTE] Release Maven Javadoc Plugin version 3.3.2
+1 pon., 7 lut 2022 o 22:12 Michael Osipov napisał(a): > Hi, > > We solved 3 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317529=12350586 > > There are still a couple of issues left in JIRA: > https://issues.apache.org/jira/projects/MJAVADOC/issues > > Staging repo: > https://repository.apache.org/content/repositories/maven-1707/ > > https://repository.apache.org/content/repositories/maven-1707/org/apache/maven/plugins/maven-javadoc-plugin/3.3.2/maven-javadoc-plugin-3.3.2-source-release.zip > > Source release checksum(s): > maven-javadoc-plugin-3.3.2-source-release.zip > sha512: > > 9fccfb11919f50615c91b699cef0edf241eae9f956be4cb2ebb67855823473c3e4ba5acd6b1419dcf274ec72ee202e2b534a1c9a5c471f2e4dd0a598b46fc232 > > Staging site: > https://maven.apache.org/plugins-archives/maven-javadoc-plugin-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 > > -- Sławomir Jaranowski
