Re: Proxy and Aether resolver configuration guide
Howdy, the "documented ways" are assumed to be as you say: settings.xml https://maven.apache.org/settings.html The properties are not recommended as that assumes per JVM configuration and may cause issues like unexpected behaviour (the message is simply "be explicit in settings.xml instead..."). For the list of supported properties (this is ASF httpClient specific, and WHEN ENABLED) are these: https://javadoc.io/static/org.apache.httpcomponents/httpclient/4.5.14/org/apache/http/impl/client/HttpClientBuilder.html So a) "documented way of [maven] configuration is settings.xml" b) yes, sensing Java System Properties are by default disabled, you must explicitly enable that if you need it Thanks T On Wed, Aug 28, 2024 at 3:06 AM Timothy Stone wrote: > > Devs, > > Reaching out here as a contributor to To Be Continuous's Maven CI/CD > templates. > > An issue was opened more than a year ago about the changes in Maven > 3.9.x and the "configuration of proxy settings via System Properties" > being "no longer supported." > > See https://gitlab.com/to-be-continuous/maven/-/issues/39 > > In the user list, something adjacent was raised, and I think there is > something about the documentation that is creating confusion. > > Specifically, `aether.transport.apache.useSystemProperties' suggests > that a) using `http.proxy` JVM settings is no longer supported, or b) > not recommended over the "documented ways of configuration": > > > If enabled, underlying Apache HttpClient will use system properties as well > > to configure itself (typically used to set up HTTP Proxy via Java system > > properties). See HttpClientBuilder for used properties. This mode is not > > recommended, better use documented ways of configuration instead. > > But the "documented ways of configuration" are then just assumed to be > known by the reader. > > So a) what are the "documented ways of configuration"? or b) are > `http.proxy' settings indeed disabled in "auto"/"native" mode or is this > all just a misreading of the documentation and the assumption here is > settings:proxies configuration. > > Thanks! > Tim > > -- > Timothy Stone > = > Some call me ... Tim. > Husband, Father, Blogger, OSS, Wargamer, Home Brewer, and D&D > Find me on GitLab | GitHub | Linked In | MeWe | GnuPG > - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [HEADS UP] Maven Doxia 2.0.0 stack is coming
Am 2024-08-28 um 03:27 schrieb Basil Crow: Hi Michael, Many thanks for your hard work on this stack over the past three years. Is Maven Fluido Skin 2.0.0-M10 safe to adopt? I notice Dependabot is not offering it because of its milestone status, but Dependabot is offering Maven Site Plugin 3.20.0, which seems to require a newer version of Maven Fluido Skin to avoid [ERROR] Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.20.0:site (default-site) on project jellydoc-maven-plugin: Failed to create context for skin: Cannot use skin: has [1.11.1,2.0.0-M1) Doxia Sitetools prerequisite, but current is 2.0.0-M19 Is there a plan to release a non-milestone version of Maven Fluido Skin? Please use 3.20.0 with Fluido Skin 2.0.0-M10. It will work. According to my plan the GA versions are about to be released from end of September. See the timeline in the headsup annoucement. Michael - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [HEADS UP] Maven Doxia 2.0.0 stack is coming
Michael, Is it worth updating our Maven Parent pom with released versions or should we wait until Doxia 2 GA? Sylwester śr., 28 sie 2024, 13:21 użytkownik Michael Osipov napisał: > Am 2024-08-28 um 03:27 schrieb Basil Crow: > > Hi Michael, > > > > Many thanks for your hard work on this stack over the past three > > years. Is Maven Fluido Skin 2.0.0-M10 safe to adopt? I notice > > Dependabot is not offering it because of its milestone status, but > > Dependabot is offering Maven Site Plugin 3.20.0, which seems to > > require a newer version of Maven Fluido Skin to avoid > > > >> [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-site-plugin:3.20.0:site (default-site) on > project jellydoc-maven-plugin: Failed to create context for skin: Cannot > use skin: has [1.11.1,2.0.0-M1) Doxia Sitetools prerequisite, but current > is 2.0.0-M19 > > > > Is there a plan to release a non-milestone version of Maven Fluido Skin? > > Please use 3.20.0 with Fluido Skin 2.0.0-M10. It will work. > > According to my plan the GA versions are about to be released from end > of September. See the timeline in the headsup annoucement. > > Michael > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
Re: [HEADS UP] Maven Doxia 2.0.0 stack is coming
Am 2024-08-28 um 13:37 schrieb Sylwester Lachiewicz: Michael, Is it worth updating our Maven Parent pom with released versions or should we wait until Doxia 2 GA? For now, I would actually obstain and give the community at least a month to absorb new versions and report issues. As soon as I start releasing GA versions (end of September) I am good in upgrading to those Doxia 2 compatible versions. Michael - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Proxy and Aether resolver configuration guide
On 8/28/24 5:42 AM, Tamás Cservenák wrote: Howdy, the "documented ways" are assumed to be as you say: settings.xml https://maven.apache.org/settings.html The properties are not recommended as that assumes per JVM configuration and may cause issues like unexpected behaviour (the message is simply "be explicit in settings.xml instead..."). For the list of supported properties (this is ASF httpClient specific, and WHEN ENABLED) are these: https://javadoc.io/static/org.apache.httpcomponents/httpclient/4.5.14/org/apache/http/impl/client/HttpClientBuilder.html So a) "documented way of [maven] configuration is settings.xml" b) yes, sensing Java System Properties are by default disabled, you must explicitly enable that if you need it Thanks T Thank you! for the clarification. I take this back to the TBC team. Tim On Wed, Aug 28, 2024 at 3:06 AM Timothy Stone wrote: Devs, Reaching out here as a contributor to To Be Continuous's Maven CI/CD templates. An issue was opened more than a year ago about the changes in Maven 3.9.x and the "configuration of proxy settings via System Properties" being "no longer supported." See https://gitlab.com/to-be-continuous/maven/-/issues/39 In the user list, something adjacent was raised, and I think there is something about the documentation that is creating confusion. Specifically, `aether.transport.apache.useSystemProperties' suggests that a) using `http.proxy` JVM settings is no longer supported, or b) not recommended over the "documented ways of configuration": If enabled, underlying Apache HttpClient will use system properties as well to configure itself (typically used to set up HTTP Proxy via Java system properties). See HttpClientBuilder for used properties. This mode is not recommended, better use documented ways of configuration instead. But the "documented ways of configuration" are then just assumed to be known by the reader. So a) what are the "documented ways of configuration"? or b) are `http.proxy' settings indeed disabled in "auto"/"native" mode or is this all just a misreading of the documentation and the assumption here is settings:proxies configuration. Thanks! Tim -- Timothy Stone = Some call me ... Tim. Husband, Father, Blogger, OSS, Wargamer, Home Brewer, and D&D Find me on GitLab | GitHub | Linked In | MeWe | GnuPG - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Timothy Stone = Some call me ... Tim. Husband, Father, Blogger, OSS, Wargamer, Home Brewer, and D&D Find me on GitLab | GitHub | Linked In | MeWe | GnuPG OpenPGP_signature.asc Description: OpenPGP digital signature
[VOTE] Release Apache Maven Filtering 3.4.0
Hi, We solved 1 issue: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922&version=12354380&styleName=Text There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHARED%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20maven-filtering Staging repo: https://repository.apache.org/content/repositories/maven-2200/ https://repository.apache.org/content/repositories/maven-2200/org/apache/maven/shared/maven-filtering/3.4.0/maven-filtering-3.4.0-source-release.zip Source release checksum(s): maven-filtering-3.4.0-source-release.zip sha512: ee25a4b337983011a2a733372f0f2fe4e344437096087ea1fa95da9281b780950bea772a9e7ee9961f573892ef12c4b01e4dc738a2479534e2f4922f37ffe5bb Staging site: https://maven.apache.org/shared-archives/maven-archiver-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 Thanks in advance for checking the release, Konrad - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven Filtering 3.4.0
Am 2024-08-28 um 17:47 schrieb Konrad Windszus: Hi, We solved 1 issue: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922&version=12354380&styleName=Text There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHARED%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20maven-filtering Staging repo: https://repository.apache.org/content/repositories/maven-2200/ https://repository.apache.org/content/repositories/maven-2200/org/apache/maven/shared/maven-filtering/3.4.0/maven-filtering-3.4.0-source-release.zip Source release checksum(s): maven-filtering-3.4.0-source-release.zip sha512: ee25a4b337983011a2a733372f0f2fe4e344437096087ea1fa95da9281b780950bea772a9e7ee9961f573892ef12c4b01e4dc738a2479534e2f4922f37ffe5bb Staging site: https://maven.apache.org/shared-archives/maven-archiver-LATEST/ Guide to testing staged releases: https://maven.apache.org/guides/development/guide-testing-releases.html Vote open for at least 72 hours. +1 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Proxy and Aether resolver configuration guide
Tangentially related: Is there a CLI method of activating a proxy by id, i.e., similar to `-P|--activate-profiles` in a POM? Thanks! Tim On 8/28/24 8:04 AM, Timothy Stone wrote: On 8/28/24 5:42 AM, Tamás Cservenák wrote: Howdy, the "documented ways" are assumed to be as you say: settings.xml https://maven.apache.org/settings.html The properties are not recommended as that assumes per JVM configuration and may cause issues like unexpected behaviour (the message is simply "be explicit in settings.xml instead..."). For the list of supported properties (this is ASF httpClient specific, and WHEN ENABLED) are these: https://javadoc.io/static/org.apache.httpcomponents/httpclient/4.5.14/ org/apache/http/impl/client/HttpClientBuilder.html So a) "documented way of [maven] configuration is settings.xml" b) yes, sensing Java System Properties are by default disabled, you must explicitly enable that if you need it Thanks T Thank you! for the clarification. I take this back to the TBC team. Tim On Wed, Aug 28, 2024 at 3:06 AM Timothy Stone wrote: Devs, Reaching out here as a contributor to To Be Continuous's Maven CI/CD templates. An issue was opened more than a year ago about the changes in Maven 3.9.x and the "configuration of proxy settings via System Properties" being "no longer supported." See https://gitlab.com/to-be-continuous/maven/-/issues/39 In the user list, something adjacent was raised, and I think there is something about the documentation that is creating confusion. Specifically, `aether.transport.apache.useSystemProperties' suggests that a) using `http.proxy` JVM settings is no longer supported, or b) not recommended over the "documented ways of configuration": If enabled, underlying Apache HttpClient will use system properties as well to configure itself (typically used to set up HTTP Proxy via Java system properties). See HttpClientBuilder for used properties. This mode is not recommended, better use documented ways of configuration instead. But the "documented ways of configuration" are then just assumed to be known by the reader. So a) what are the "documented ways of configuration"? or b) are `http.proxy' settings indeed disabled in "auto"/"native" mode or is this all just a misreading of the documentation and the assumption here is settings:proxies configuration. Thanks! Tim -- Timothy Stone = Some call me ... Tim. Husband, Father, Blogger, OSS, Wargamer, Home Brewer, and D&D Find me on GitLab | GitHub | Linked In | MeWe | GnuPG - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Timothy Stone = Some call me ... Tim. Husband, Father, Blogger, OSS, Wargamer, Home Brewer, and D&D Find me on GitLab | GitHub | Linked In | MeWe | GnuPG OpenPGP_signature.asc Description: OpenPGP digital signature
Re: [HEADS UP] Maven Doxia 2.0.0 stack is coming
> * Other reporting plugins we provide are not being upgraded Are those other plugins no longer supported by the Maven team? Looking at https://maven.apache.org/plugins/ The changelog, changes, and linkcheck plugins look to be the only three reporting plugins not being upgraded. On Tue, Jul 9, 2024 at 10:30 AM Michael Osipov wrote: > Dear Users, Reporting Plugin and Skin Maintainers, > > for the past 2,5 years we have been working -- that is me (mostly) with > Hervé Boutemy and Konrad Windszus -- on the modernization of the Doxia > stack overcoming technical debts and open issues of the past ten years. > After numerous milestones (10+) it has reached a very good maturity and > stability to finally move to GA. > > What is Maven Doxia anyway? It is the core document generation framework > on which all Maven reporting plugins and the Maven Site Plugin are built > upon. So when you invoke a standalone reporting goal or "mvn site" that > stack is being used. > The involved components and reporting plugins from the Maven Core Team: > * maven-doxia > * maven-reporting-api > * maven-doxia-sitetools > * maven-reporting-impl > * maven-reporting-exec > * maven-site-plugin > * maven-fluido-skin > * maven-project-info-reports-plugin > * maven-plugin-tools (maven-plugin-reporting-plugin) > * maven-jxr (maven-jxr-plugin) > * maven-pmd-plugin > * maven-javadoc-plugin > * maven-checkstyle-plugin > * maven-help-plugin (uses API only) > * maven-surefire (maven-surefire-report-plugin) > * maven-dependency-plugin > * maven-invoker-plugin > > Notes: > * Other reporting plugins we provide are not being upgraded > * Third party plugins need to be upgraded by their respective maintainers > * Components do have milestone versions until public evaluation has been > completed > > Also, please see this Confluence Wiki entry for more (technical) > details: > https://cwiki.apache.org/confluence/display/MAVEN/Towards+Doxia+2.0.0+Stack > > What do you need to do? > * As a user you can build the reporting plugins from the prepared branch > 'doxia-2.0.0' or reach out to the third party maintainer to test his > plugin against the updated stack. > * As a plugin maintainer you can start upgrading your plugin against the > 2.0.0 baseline in a separate branch. Look at the 'doxia-2.0.0' branch of > our plugins to ease your work. > * As a skin maintainer you can start upgrading your skin against the > 2.0.0 baseline in a separate branch. Look at the master branch of the > maven-fluido-skin. to ease your work. > > Found problems, issues or have questions? Please report via users@ or > dev@ mailing list (whichever makes most sense) and prepend "[DOXIA]" to > the subject. I will try to respond timely. > > Expectations: > * If you intend to mix and match components and plugins between both > major versions (Doxia 1.x vs. Doxia 2.x) you must use the highest > maven-site-plugin version, but don't expect everything to go smoothly. > * Not every issue or behavioral change is a regression. Some changes are > deliberate. If they are not listed in the Confluence Wiki page, let me > know, I will add them. But in any case, feel free to reach out. > > Timeline: > * By mid of July I will give the the public (users and maintainers) at > least 30 days (but no later than 2024-08-15) to review the changes in > the stack, the 'doxia-2.0.0' branches, evaluate your plugin upgrade path > and/or release new versions of plugins with old stack. > * By mid of August I will start merging the 'doxia-2.0.0' branches into > every of our reporting plugins and perform the release procedure. > * After the reporting plugins from us (Maven Core Team) have been > released I will again give the public at least 30 days (but no later > than 2024-10-15) to review the upgraded and released plugins. > * If no issues are reported against components or plugins until mid of > October I will move all Doxia stack milestone components to a GA version > and release the reporting plugins with those GA versions. > * At least six or twelve months after that we might remove deprecated > code from the Doxia 2.0.0 stack likely breaking code which worked > transitionally. > > Versioning: > Components have been bumped to new major versions. Plugin versions will > remain on 3.x due to Maven 3 compatiblity. Their minor versions will be > bumped. Maven Site Plugin 4 will be retained for future Maven 4, a new > branch for Maven Site Plugin 3.x (likely 3.20.0) will be created and all > changed will be merged into that branch. The current 3.x branch will be > renamed to 3.12.x. > > I hope to complete the GA release train by end of 2024 -- after more > than three years! > > Good luck, > > Michael >
Re: [HEADS UP] Maven Doxia 2.0.0 stack is coming
Am 2024-08-28 um 18:59 schrieb Matt Nelson: * Other reporting plugins we provide are not being upgraded Are those other plugins no longer supported by the Maven team? Looking at https://maven.apache.org/plugins/ The changelog, changes, and linkcheck plugins look to be the only three reporting plugins not being upgraded. That is correct. In fact, regarding the Changes Plugin I have written a lengthly mail to the dev@ mailing list and what's wrong with it. No one stood up to volunteer to move to it Doxia 2.0.0. The other two have been dead already. We just need to make it official which -- again -- needs time. Michael - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Disable ASF GitHub Bot comments in JIRA
Hi everyone, I consider the automatic JIRA comments being added for each GitHub PR comment quite verbose and redundant. Also the formatting is in some cases broken because it doesn’t properly escape for the Confluence markdown used by JIRA (e.g. look at https://issues.apache.org/jira/browse/MRELEASE-1154?page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel&focusedCommentId=17877317#comment-17877317). I would propose to disable the automatic commenting via the .asf.yaml [1] by just setting jira_options: link label Instead of jira_options: link label comment @Herve: Since you added it explicitly via e.g. https://github.com/apache/maven-release/commit/78e2329b2aee142563d5fd93feda216e04662bdc or https://github.com/apache/maven-site-plugin/commit/75c8d35df293a4e0defa5c7ac1092c7984e0f93d I am wondering what the intention was…. WDYT? Konrad [1] - https://github.com/apache/infrastructure-asfyaml?tab=readme-ov-file#jira-notification-options - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
