Re: Removing IRC channel mentions from official website documentation
As one of the new guys, I can confirm that IRC is misleading and confusing. I totally missed any topic regarding the "we moved to slack" part. Could've been a bad IRC client, could've been me, not sure. I agree with Bernd: New people would very much like to find slack information on the website, even though access is restricted. And yes, mentioning who gets access and how would help a great deal, I think, albeit just for clarification. Kind regards Enno From: Bernd Eckenfels Sent: Wednesday, September 8, 2021 10:30 PM To: Maven Developers List Subject: Re: Removing IRC channel mentions from official website documentation Thanks for bringing this to our attention and I agree we should remove the irc channel in this case. Not sure about the slack since I don’t use it, but the website is not only for the public, it’s also the primary source for committers (but if we add the slack we certainly need to mention who gets access and how) On what URLs you saw the irc channel? Gruss Bernd -- http://bernd.eckenfels.net Von: Dawid Pura Gesendet: Wednesday, September 8, 2021 10:16:27 PM An: dev@maven.apache.org Betreff: Removing IRC channel mentions from official website documentation Hello all, I have noticed it's misleading for new contributors to find out the proper communication channel for this project. The documentation says there is an IRC channel which topic says "we moved to Slack". Then, it takes some time to figure out a newcomer cannot get in, since she has to be invited by actual commiters. I think I can remove any mention of IRC channel from maven-site, as this has been deprecated comms channel, right? I am asking the more subtle question, should the Slack channel be mentioned instead, or there is no reason to mention it in public docs as it's not reachable by the public. this is my very first e-mail on this mailing list and mailing lists in Apache in general, so please share any feedback that comes to your mind :). All the best, Dawid Pura
Re: Removing IRC channel mentions from official website documentation
Thanks for bringing this to our attention and I agree we should remove the irc channel in this case. Not sure about the slack since I don’t use it, but the website is not only for the public, it’s also the primary source for committers (but if we add the slack we certainly need to mention who gets access and how) On what URLs you saw the irc channel? Gruss Bernd -- http://bernd.eckenfels.net Von: Dawid Pura Gesendet: Wednesday, September 8, 2021 10:16:27 PM An: dev@maven.apache.org Betreff: Removing IRC channel mentions from official website documentation Hello all, I have noticed it's misleading for new contributors to find out the proper communication channel for this project. The documentation says there is an IRC channel which topic says "we moved to Slack". Then, it takes some time to figure out a newcomer cannot get in, since she has to be invited by actual commiters. I think I can remove any mention of IRC channel from maven-site, as this has been deprecated comms channel, right? I am asking the more subtle question, should the Slack channel be mentioned instead, or there is no reason to mention it in public docs as it's not reachable by the public. this is my very first e-mail on this mailing list and mailing lists in Apache in general, so please share any feedback that comes to your mind :). All the best, Dawid Pura
[VOTE] Release Maven Resolver version 1.7.2
Hi, We solved 13 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628=12344271 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRESOLVER%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20Resolver Staging repo: https://repository.apache.org/content/repositories/maven-1664/ https://repository.apache.org/content/repositories/maven-1664/org/apache/maven/resolver/maven-resolver/1.7.2/maven-resolver-1.7.2-source-release.zip Source release checksum(s): maven-resolver-1.7.2-source-release.zip 793ea97d055e9b9ce0555427985a0e3c04b0c68342d1b67c1f42cd8a42354f0736e02f312cb1622d489504767d45ddaef2bd3d4b9de161bb6d9ec78eac677b59 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 72 hours. [ ] +1 [ ] +0 [ ] -1 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Removing IRC channel mentions from official website documentation
Hello all, I have noticed it's misleading for new contributors to find out the proper communication channel for this project. The documentation says there is an IRC channel which topic says "we moved to Slack". Then, it takes some time to figure out a newcomer cannot get in, since she has to be invited by actual commiters. I think I can remove any mention of IRC channel from maven-site, as this has been deprecated comms channel, right? I am asking the more subtle question, should the Slack channel be mentioned instead, or there is no reason to mention it in public docs as it's not reachable by the public. this is my very first e-mail on this mailing list and mailing lists in Apache in general, so please share any feedback that comes to your mind :). All the best, Dawid Pura
[GitHub] [maven-site] michael-o commented on pull request #259: guide-site.apt: fix typo in mvn command
michael-o commented on pull request #259: URL: https://github.com/apache/maven-site/pull/259#issuecomment-915504649 Obrigado! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[GitHub] [maven-site] michael-o merged pull request #259: guide-site.apt: fix typo in mvn command
michael-o merged pull request #259: URL: https://github.com/apache/maven-site/pull/259 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[GitHub] [maven-site] waldyrious opened a new pull request #259: guide-site.apt: fix typo in mvn command
waldyrious opened a new pull request #259: URL: https://github.com/apache/maven-site/pull/259 Just a one-character fix, but it was enough to confuse me for a bit. :sweat_smile: Since there's already a `site-deploy` phase in the built-in `site` lifecycle, I thought perhaps there was also a `site-stage` phase, and went looking around for it to understand why it wasn't mentioned in the list of phases of the site lifecycle (and of course I didn't find it.) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - 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
Sounds good Michael, thanks for the update. Gary On Sun, Sep 5, 2021, 12:50 Michael Osipov wrote: > 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 .invalid> > > 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 .INVALID>: > >>> > 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=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 > >> > >> > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
[GitHub] [maven-artifact-transfer] michael-o edited a comment on pull request #24: [MSHARED-987] Make use of SISU
michael-o edited a comment on pull request #24: URL: https://github.com/apache/maven-artifact-transfer/pull/24#issuecomment-915321903 Question to reviews: Do we really need Sisu support for Maven 3.0.x? I'd rather drop it and focus on 3.1.x+ only. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[GitHub] [maven-artifact-transfer] michael-o commented on pull request #24: [MSHARED-987] Make use of SISU
michael-o commented on pull request #24: URL: https://github.com/apache/maven-artifact-transfer/pull/24#issuecomment-915321903 Question to reviews. Do we really need Sisu support for Maven 3.0.x? I'd rather drop it and focus on 3.1.x+ only. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[GitHub] [maven-artifact-transfer] michael-o commented on pull request #24: [MSHARED-987] Make use of SISU
michael-o commented on pull request #24: URL: https://github.com/apache/maven-artifact-transfer/pull/24#issuecomment-915269142 Maven Deploy Plugin must be tested. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[GitHub] [maven-artifact-transfer] slachiewicz merged pull request #45: Bump groovy from 3.0.8 to 3.0.9
slachiewicz merged pull request #45: URL: https://github.com/apache/maven-artifact-transfer/pull/45 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[GitHub] [maven-artifact-transfer] dependabot[bot] opened a new pull request #45: Bump groovy from 3.0.8 to 3.0.9
dependabot[bot] opened a new pull request #45: URL: https://github.com/apache/maven-artifact-transfer/pull/45 Bumps [groovy](https://github.com/apache/groovy) from 3.0.8 to 3.0.9. Commits See full diff in https://github.com/apache/groovy/commits;>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Feature proposal: Dependency deprecation indicators
I have now created a Jira issue to move this forward: https://issues.apache.org/jira/browse/MNG-7238 Regards, Chris - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[GitHub] [maven-artifact-transfer] cstamas commented on pull request #24: [MSHARED-987] Make use of SISU
cstamas commented on pull request #24: URL: https://github.com/apache/maven-artifact-transfer/pull/24#issuecomment-915140926 > To me the change is too big to validate, so it must proof itself for the several plugins out there that depend on it. Ok, @slachiewicz tested with m-dependency-p, which other plugins you have on your mind? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[GitHub] [maven-artifact-transfer] rfscholte commented on pull request #24: [MSHARED-987] Make use of SISU
rfscholte commented on pull request #24: URL: https://github.com/apache/maven-artifact-transfer/pull/24#issuecomment-915137419 To me the change is too big to validate, so it must proof itself for the several plugins out there that depend on it. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[GitHub] [maven-artifact-transfer] cstamas commented on pull request #24: [MSHARED-987] Make use of SISU
cstamas commented on pull request #24: URL: https://github.com/apache/maven-artifact-transfer/pull/24#issuecomment-915128652 Any other comment? I'd like to merge or drop this, is lingering for way too long... -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Initialisation of a vote for Maven Shade Plugin version 3.3.0
Hi, I hope someone from the maintainers can cut a new Maven Shade Plugin release and initialise a new VOTE for Maven Shade Plugin version 3.3.0. I checked the last voting thread (https://lists.apache.org/thread.html/rb9f899586cf49fefffc291b028a14b5fa8e22797d79d2362bcdfb58c%40%3Cdev.maven.apache.org%3E) and it seems that the pull requests that were blocking publication have now been merged. Best Regards Philipp - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
