Re: Regression in Maven 3.8.2? site/javadoc generation fails
Gary, I plan to address open issues in the course of the next two weeks. Followed by week of testing by the community. If everything goes well I will call the vote by the end of this month. M Am 2021-09-05 um 16:46 schrieb Gary Gregory: Hopefully 3.8.3 is around the corner. Gary On Sat, Sep 4, 2021, 11:09 Stefan Seifert wrote: hello falko. i can confirm the problem is fixed with PR #527! - will add a comment to about it in MNG-7220. stefan -Original Message- From: Falko Modler Sent: Saturday, September 4, 2021 12:39 PM To: Maven Developers List Subject: Re: Regression in Maven 3.8.2? site/javadoc generation fails I haven't checked, but there is a good chance https://github.com/apache/maven/pull/527 might fix that problem. Cheers, Falko 03.09.2021 16:02:04 Stefan Seifert : thanks for the pointer - but i think my problem is different. in my case it's not a problem of looking up a site descriptor, but resolving dependencies from parent POMs during the javadoc generation that is part of the site build. i tried the tarball from https://issues.apache.org/jira/browse/MNG- 7218?focusedCommentId=17400589&page=com.atlassian.jira.plugin.system.issuet abpanels:comment-tabpanel#comment-17400589 which reverts the change from MGN-7170, and it fixes the problem with getting the right skin for the site, but did not fix the problem with the dependencies in javadoc generation described here initially. should i create a new MNG issue for it? stefan -Original Message- From: Gary Gregory Sent: Friday, September 3, 2021 2:41 PM To: Maven Developers List Subject: Re: Regression in Maven 3.8.2? site/javadoc generation fails See https://issues.apache.org/jira/browse/MNG-7215 and the short thread here "Wrong site skin in 3.8.2 vs 3.6.3" Gary On Fri, Sep 3, 2021, 08:08 Stefan Seifert wrote: i've encountered a problem in numerous of our Maven builds at wcm.io [1] which started failing yesterday when GitHub switched to latest Maven 3.8.2 release for their images. an example is described in [2], build log [3], to sum it up: - build fails in when generating the maven site during the javadoc step, which is unable to find a couple of dependencies which are defined correctly (they are defined as "provided" in the section of one of the parent POMs) - the build does not fail when "javadoc:javadoc" is executed directly, only as part of the "site" goal - everything runs fine with Maven 3.8.1 or 3.6.3 i'm not sure if this is an issue in either site mojo or javadoc mojo or Maven itself. the release notes [4] contain a pointer to a change around MNG-6843, but i'm not aware that site or javadoc plugin are spwaning new threads. any ideas about the root cause? stefan [1] https://github.com/wcm-io [2] https://wcm-io.atlassian.net/browse/WTOOL-78 [3] https://github.com/wcm-io/wcm-io-wcm-core- components/runs/3505611228?check_suite_focus=true [4] https://maven.apache.org/docs/3.8.2/release-notes.html - 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 - 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: Testing staged release
good catch I did a first pass at using some of your points: don't hesitate to prpose other improvements Notice: on your questions, I don't really have any answer, these should probably be asked to infra who is managing the repository manager configuration Regards, Hervé Le samedi 4 septembre 2021, 16:40:44 CEST Slawomir Jaranowski a écrit : > Hi, > > It looks like "Guide to Testing Staged Releases" [1] is something outdated > and not consistent with "Performing a Maven Project Release" [2] > > In [1] we have example with repository location like > http://people.apache.org/~dfabulich/stage-repo > but in [2] we heve staging repo as > https://repository.apache.org/content/repositories/maven-[YOUR REPOSITORY > ID]/ > > [2] point to [1] so both pages should be consistent. > > I also found that Apache Repository [3] contains two groups: Maven Staging > Group [4] and Staging [5]. > Both of this group contains new staged items like last Apache Maven Javadoc > Plugin version 3.3.1 > > So I prepare config with additional profiles pointing to one of this staged > repository and I can perform tests for the new plugin. > It will be easier to have one configuration for all stages testing - > without changing stage id. > > When I use properties for version in project and have stage profile I can > simply run like > >mvn -P apache-stage -Dmaven-javadoc-plugin.version=3.3.1 javadoc:javadoc > > without additional configuration. > > Now questions: > 1. Can I use one of those repositories for testing staged releases (which > is preferred)? > 2. What is different in contend in Maven Staging Group [4] and Staging [5]? > 3. Are staged repository groups [4], [5] cleaned - if yes when? > > [1] https://maven.apache.org/guides/development/guide-testing-releases.html > [2] > https://maven.apache.org/developers/release/maven-project-release-procedure. > html [3] https://repository.apache.org/#view-repositories > [4] https://repository.apache.org/content/groups/maven-staging-group/ > [5] https://repository.apache.org/content/groups/staging/ - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Regression in Maven 3.8.2? site/javadoc generation fails
Hopefully 3.8.3 is around the corner. Gary On Sat, Sep 4, 2021, 11:09 Stefan Seifert wrote: > hello falko. > > i can confirm the problem is fixed with PR #527! - will add a comment to > about it in MNG-7220. > > stefan > > >-Original Message- > >From: Falko Modler > >Sent: Saturday, September 4, 2021 12:39 PM > >To: Maven Developers List > >Subject: Re: Regression in Maven 3.8.2? site/javadoc generation fails > > > >I haven't checked, but there is a good chance > >https://github.com/apache/maven/pull/527 might fix that problem. > > > >Cheers, > > > >Falko > > > >03.09.2021 16:02:04 Stefan Seifert : > > > >> thanks for the pointer - but i think my problem is different. in my case > >it's not a problem of looking up a site descriptor, but resolving > >dependencies from parent POMs during the javadoc generation that is part > of > >the site build. > >> > >> i tried the tarball from https://issues.apache.org/jira/browse/MNG- > > >7218?focusedCommentId=17400589&page=com.atlassian.jira.plugin.system.issuet > >abpanels:comment-tabpanel#comment-17400589 which reverts the change from > >MGN-7170, and it fixes the problem with getting the right skin for the > >site, but did not fix the problem with the dependencies in javadoc > >generation described here initially. > >> > >> should i create a new MNG issue for it? > >> > >> stefan > >> > >>> -Original Message- > >>> From: Gary Gregory > >>> Sent: Friday, September 3, 2021 2:41 PM > >>> To: Maven Developers List > >>> Subject: Re: Regression in Maven 3.8.2? site/javadoc generation fails > >>> > >>> See https://issues.apache.org/jira/browse/MNG-7215 and the short > thread > >>> here "Wrong site skin in 3.8.2 vs 3.6.3" > >>> > >>> Gary > >>> > >>> On Fri, Sep 3, 2021, 08:08 Stefan Seifert >>> e.com.invalid> > >>> wrote: > >>> > i've encountered a problem in numerous of our Maven builds at wcm.io > >[1] > which started failing yesterday when GitHub switched to latest Maven > >>> 3.8.2 > release for their images. > > an example is described in [2], build log [3], to sum it up: > - build fails in when generating the maven site during the javadoc > >step, > which is unable to find a couple of dependencies which are defined > correctly (they are defined as "provided" in the section > >of > one of the parent POMs) > - the build does not fail when "javadoc:javadoc" is executed directly, > only as part of the "site" goal > - everything runs fine with Maven 3.8.1 or 3.6.3 > > i'm not sure if this is an issue in either site mojo or javadoc mojo > or > Maven itself. the release notes [4] contain a pointer to a change > >around > MNG-6843, but i'm not aware that site or javadoc plugin are spwaning > >new > threads. > > any ideas about the root cause? > > stefan > > [1] https://github.com/wcm-io > [2] https://wcm-io.atlassian.net/browse/WTOOL-78 > [3] > https://github.com/wcm-io/wcm-io-wcm-core- > >>> components/runs/3505611228?check_suite_focus=true > [4] https://maven.apache.org/docs/3.8.2/release-notes.html > > - > 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 > >> > > > >- > >To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > >For additional commands, e-mail: dev-h...@maven.apache.org > >
[VOTE] Release Apache Maven WAR Plugin version 3.3.2
Hi, We solved 2 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318121&version=12348574&styleName=Text Staging repo: https://repository.apache.org/content/repositories/maven-1661/ https://repository.apache.org/content/repositories/maven-1661/org/apache/maven/plugins/maven-war-plugin/3.3.2/maven-war-plugin-3.3.2-source-release.zip Source release checksum(s): maven-war-plugin-3.3.2-source-release.zip sha512: 368d1066d3aa429b3dc26b1e3a502fe56c4232fae13727c74d44015b160eec3753f28ff72e3a0f33f9dfa9d25e9912efb559d45cf41952151ecc88337203fc95 Staging site: https://maven.apache.org/plugins-archives/maven-war-plugin-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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
