Re: maven.repo.local cf. localRepository
Howdy Yes, usually you do want it absolute. The relative examples like "-Dmaven repo.local=../repo" you usually can find in some examples or reproducers. If local repo path relative, these will end up using different local repositories (imagine some multi module build): $ mvn install $ mvn -f submodule1/pom.xml install $ cd submodule2 && mvn install As it is evaluated at maven boot and relative would be calculated against CWD based on invocation (plus, -f modifies it). Hth T On Sun, Jul 14, 2024, 03:10 Timothy Stone wrote: > I help maintain Maven tooling for To Be Continuous, a GitLab CI/CD > catalog of pluggable pipeline configurations. > > There is some discussion on the use of the JVM property, > `-Dmaven.repo.local=path' and the note on "Configuring your Local > Repository" (see [1]). Initially I was going to post to the user list, > but being a development question against the internals of Maven, I > thought this a better forum. > > There is an admonition on the referenced page: > > /Note: The local repository _must_ be an absolute path./ (emphasis mine) > > Is this specifically noted for the use of the settings.localRepository > only or does the note extend to the use of the JVM property? I searched > the GitHub repo for a examples and found numerous uses of relative > paths, e.g., `../.repository` and others. > > Seeking clarification as I could not immediately determine the internal > use of `maven.repo.local' property when set. > > Thanks! > Tim > > > [1] > > https://maven.apache.org/guides/mini/guide-configuring-maven.html#configuring-your-local-repository > -- > 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 >
Re: maven.repo.local cf. localRepository
Hi Agree it should be absolute but there is no technical constraint - ultimately it must be known how it resolves. I know on ci it is common to use a relative path to avoid ci specific internal path issues accross os/workers. Le dim. 14 juil. 2024 à 09:52, Tamás Cservenák a écrit : > Howdy > > Yes, usually you do want it absolute. > > The relative examples like "-Dmaven repo.local=../repo" you usually can > find in some examples or reproducers. > > If local repo path relative, these will end up using different local > repositories (imagine some multi module build): > > $ mvn install > $ mvn -f submodule1/pom.xml install > $ cd submodule2 && mvn install > > As it is evaluated at maven boot and relative would be calculated against > CWD based on invocation (plus, -f modifies it). > > Hth > T > > On Sun, Jul 14, 2024, 03:10 Timothy Stone wrote: > > > I help maintain Maven tooling for To Be Continuous, a GitLab CI/CD > > catalog of pluggable pipeline configurations. > > > > There is some discussion on the use of the JVM property, > > `-Dmaven.repo.local=path' and the note on "Configuring your Local > > Repository" (see [1]). Initially I was going to post to the user list, > > but being a development question against the internals of Maven, I > > thought this a better forum. > > > > There is an admonition on the referenced page: > > > > /Note: The local repository _must_ be an absolute path./ (emphasis mine) > > > > Is this specifically noted for the use of the settings.localRepository > > only or does the note extend to the use of the JVM property? I searched > > the GitHub repo for a examples and found numerous uses of relative > > paths, e.g., `../.repository` and others. > > > > Seeking clarification as I could not immediately determine the internal > > use of `maven.repo.local' property when set. > > > > Thanks! > > Tim > > > > > > [1] > > > > > https://maven.apache.org/guides/mini/guide-configuring-maven.html#configuring-your-local-repository > > -- > > 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 > > >
Re: maven.repo.local cf. localRepository
Using relative path can have some surprises, so I would avoid it whenever possible. Especially on CI there is usually an (absolute) workspace path available. Technically the JVM will transform a relative path into an absolute one by using the currents process working directory but "relative" might be surprising on some filesystems/os depending on how the string is passed to Java API. Am 14.07.24 um 16:04 schrieb Romain Manni-Bucau: Hi Agree it should be absolute but there is no technical constraint - ultimately it must be known how it resolves. I know on ci it is common to use a relative path to avoid ci specific internal path issues accross os/workers. Le dim. 14 juil. 2024 à 09:52, Tamás Cservenák a écrit : Howdy Yes, usually you do want it absolute. The relative examples like "-Dmaven repo.local=../repo" you usually can find in some examples or reproducers. If local repo path relative, these will end up using different local repositories (imagine some multi module build): $ mvn install $ mvn -f submodule1/pom.xml install $ cd submodule2 && mvn install As it is evaluated at maven boot and relative would be calculated against CWD based on invocation (plus, -f modifies it). Hth T On Sun, Jul 14, 2024, 03:10 Timothy Stone wrote: I help maintain Maven tooling for To Be Continuous, a GitLab CI/CD catalog of pluggable pipeline configurations. There is some discussion on the use of the JVM property, `-Dmaven.repo.local=path' and the note on "Configuring your Local Repository" (see [1]). Initially I was going to post to the user list, but being a development question against the internals of Maven, I thought this a better forum. There is an admonition on the referenced page: /Note: The local repository _must_ be an absolute path./ (emphasis mine) Is this specifically noted for the use of the settings.localRepository only or does the note extend to the use of the JVM property? I searched the GitHub repo for a examples and found numerous uses of relative paths, e.g., `../.repository` and others. Seeking clarification as I could not immediately determine the internal use of `maven.repo.local' property when set. Thanks! Tim [1] https://maven.apache.org/guides/mini/guide-configuring-maven.html#configuring-your-local-repository -- 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: maven.repo.local cf. localRepository
On 7/14/24 10:04 AM, Romain Manni-Bucau wrote: Hi Agree it should be absolute but there is no technical constraint - ultimately it must be known how it resolves. I know on ci it is common to use a relative path to avoid ci specific internal path issues accross os/workers. I concur. But as I note below, I think most CI environments can address this. Le dim. 14 juil. 2024 à 09:52, Tamás Cservenák a écrit : ... snip ... As it is evaluated at maven boot and relative would be calculated against CWD based on invocation (plus, -f modifies it). As Manni-Bucau noted above, CI workers/runners add some context to consider. In the case of GitLab, the CI context is populated with many variables that can aid in easily resolving or creating an absolute path. For example, GitLab's CI_* variables are populated and include the CI_PROJECT_DIR variable that can be used to "pin" the absolute path. I think this is enough to provide the team more information as we drive a path forward. Thanks for the detailed answer Tamás, and the additional context clarity Manni-Bacau. Hth T On Sun, Jul 14, 2024, 03:10 Timothy Stone wrote: I help maintain Maven tooling for To Be Continuous, a GitLab CI/CD catalog of pluggable pipeline configurations. There is some discussion on the use of the JVM property, `-Dmaven.repo.local=path' and the note on "Configuring your Local Repository" (see [1]). Initially I was going to post to the user list, but being a development question against the internals of Maven, I thought this a better forum. There is an admonition on the referenced page: /Note: The local repository _must_ be an absolute path./ (emphasis mine) Is this specifically noted for the use of the settings.localRepository only or does the note extend to the use of the JVM property? I searched the GitHub repo for a examples and found numerous uses of relative paths, e.g., `../.repository` and others. Seeking clarification as I could not immediately determine the internal use of `maven.repo.local' property when set. Thanks! Tim [1] https://maven.apache.org/guides/mini/guide-configuring-maven.html#configuring-your-local-repository -- 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 -- 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
[RESULT] [VOTE] Release Maven Project Info Reports Plugin version 3.6.2
Hi, The vote has passed with the following result: +1: Michael Osipov, Sylwester Lachiewicz, Slawomir Jaranowski 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
[RESULT] [VOTE] Release Maven Release version 3.1.1
Hi, The vote has passed with the following result: +1: Michael Osipov, Basil Crow, Sylwester Lachiewicz, Slawomir Jaranowski, Olivier Lamy 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
[ANN] Maven Project Info Reports Plugin 3.6.2 released
The Apache Maven team is pleased to announce the release of the Maven Project Info Reports Plugin version 3.6.2. https://maven.apache.org/plugins/maven-project-info-reports-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-project-info-reports-plugin 3.6.2 Release Notes - Maven Project Info Reports Plugin - Version 3.6.2 ** Bug * [MPIR-466] - ModulesReport/IndexReport do not pass a complete building request to renderer Enjoy, -The Apache Maven team - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[ANN] Maven Release 3.1.1 released
The Apache Maven team is pleased to announce the release of the Maven Release version 3.1.1. https://maven.apache.org/maven-release/ Release Notes - Maven Release - Version 3.1.1 ** Bug * [MRELEASE-1149] - Current release of the plugin has configuration docs missing * [MRELEASE-1151] - [REGRESSION] Maven Release Plugin fails to adjust version ** Task * [MRELEASE-1153] - Revert parts of MRELEASE-1109 (8dfcb47996320af5e6f0b2d50eac209eeb4c29ce) due to a regression Enjoy, -The Apache Maven team - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [DISCUSS] Move some mojohaus plugins to the ASF
Hi, This should be discussed at the maybe dormant but original mojohaus mailing list as well: https://www.mojohaus.org/mailing-lists.html the last few years were all about reducing code we maintain here and now we want to add more? I find the mojohaus release process very simple and quick compared to what we have here. At the end of the day it's just a github repo somewhere else where most of maven dev folks have permissions I'm not really sure what moving this here will fix except slow down the release process? - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: (maven-build-helper-plugin) branch master updated (e1873bd -> 1f32612)
-1 this doesn't look right to me to push content here without waiting for the end of discussion or vote. On Fri, 12 Jul 2024 at 16:15, wrote: > > This is an automated email from the ASF dual-hosted git repository. > > gnodet pushed a change to branch master > in repository > https://gitbox.apache.org/repos/asf/maven-build-helper-plugin.git > > > discard e1873bd Minor additional fixes > discard 5f5af25 Complete move as a maven plugin > discard 7aba0e2 Move to org.apache groupId, rename package > new 1f32612 Transform into a Maven owned plugin > > This update added new revisions after undoing existing revisions. > That is to say, some revisions that were in the old version of the > branch are not in the new version. This situation occurs > when a user --force pushes a change and generates a repository > containing something like this: > > * -- * -- B -- O -- O -- O (e1873bd) > \ > N -- N -- N refs/heads/master (1f32612) > > You should already have received notification emails for all of the O > revisions, and so the following emails describe only the N revisions > from the common base, B. > > Any revisions marked "omit" are not gone; other references still > refer to them. Any revisions marked "discard" are gone forever. > > The 1 revisions listed above as "new" are entirely new to this > repository and will be described in separate emails. The revisions > listed as "add" were already present in the repository and have only > been added to this reference. > > > Summary of changes: > pom.xml | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
