Re: ASF Maven credential in a project-wise token?

If you run the build on asf Jenkins the credentials are there. You just need to inherit from the latest apache pom and it should work. Chris Gesendet von Outlook für Android From: tison Sent: Friday, May 26, 2023 1:33:29 PM To: Maven

Re: [HEADS UP] Upcoming Resolver and Maven releases

Draft: https://github.com/apache/maven-site/pull/424 T On Fri, May 26, 2023, 22:23 Tamás Cservenák wrote: > Howdy, > > good call, created https://issues.apache.org/jira/browse/MNG-7797 > > Thanks > T > > On Fri, May 26, 2023 at 10:09 PM Henning Schmiedehausen < > henn...@schmiedehausen.org>

Re: [HEADS UP] Upcoming Resolver and Maven releases

Howdy, good call, created https://issues.apache.org/jira/browse/MNG-7797 Thanks T On Fri, May 26, 2023 at 10:09 PM Henning Schmiedehausen < henn...@schmiedehausen.org> wrote: > maven 3.9.2: > > mvn -DskipTests -Dmaven.plugin.validation=BRIEF -pl :jdbi3-core clean > install > [...] > > current

Re: [HEADS UP] Upcoming Resolver and Maven releases

maven 3.9.2: mvn -DskipTests -Dmaven.plugin.validation=BRIEF -pl :jdbi3-core clean install [...] current 3.9.3-SNAPSHOT: mvn -DskipTests -Dmaven.plugin.validation=BRIEF -pl :jdbi3-core clean install [...] *[WARNING] Invalid value specified for property maven.plugin.validation: 'BRIEF'.

Re: [VOTE] Release Maven Project Info Reports Plugin version 3.4.4

There's some dependency cleanup that could be done in this project. a couple of artifacts should be test scope and also updated to the latest versions, perhaps a few other things On Fri, May 26, 2023 at 3:29 PM Michael Osipov wrote: > > Hi, > > we solved 6 issues: >

[VOTE] Release Maven Project Info Reports Plugin version 3.4.4

Hi, we solved 6 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317821=12353222 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/projects/MPIR/issues Staging repo: https://repository.apache.org/content/repositories/maven-1948/

Re: GH issues and GH discussions

Big +1, as more and more projects are already migrating (including Apache Shiro). I'd vote for maven-jlink-plugin: Not many issues currently. > not having to create an issue if a PR exists first I'd at least make milestones mandatory in that case. It is far less work than maintaining an issue.

ASF Maven credential in a project-wise token?

Hi, I'm configuring tokens for automatically deploying artifacts to the ASF snapshot repository[1]. It requires configuring a user token to auth to the repository. Although I'm wondering if I must use my personal token or if there is some project-wise token to use. Even asking for an INFRA

Re: Is it okay to deploy additional artifacts for an identical POM? (as in MDEPLOY-118)

On Fri, May 26, 2023 at 4:18 AM Kemal Soysal wrote: > > Hi Mathias, > > I commented on the pull request. > For me it is crucial to be able to upload additional artifacts to a > coordinate. > It has various reasons. > When you work in an agile mind set, you do not need every artifact in the >

Re: [HEADS UP] Upcoming Resolver and Maven releases

Hi Tamas, I'm still getting locking issues with maven-surefire-plugin:3.1.0 I assumed these were resolved in https://issues.apache.org/jira/browse/MRESOLVER-346 which i believe made it into Maven 3.9.2, so switched back to Maven 3.9.0 What was the previous default value of

Re: Is it okay to deploy additional artifacts for an identical POM? (as in MDEPLOY-118)

Hi Mathias, I commented on the pull request. For me it is crucial to be able to upload additional artifacts to a coordinate. It has various reasons. When you work in an agile mind set, you do not need every artifact in the very beginning. You do approach agile and deliver first the most needed

Re: Is it okay to deploy additional artifacts for an identical POM? (as in MDEPLOY-118)

Hey there, I did not get a reply to this message. Does that mean, all is fine and you would like to merge the PR? (Once review comments are handled, of course.) Cheers, Mathias On Tue, May 23, 2023, at 11:16, Mathias de Riese wrote: > Hi, > > some time ago I had the problem described in >

[HEADS UP] Upcoming Resolver and Maven releases

Howdy, Resolver 1.9.11 is shaping: https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRESOLVER%20AND%20fixVersion%20%3D%201.9.11 one resolver issue under scrutiny: https://issues.apache.org/jira/browse/MRESOLVER-362 Maven 3.9.3 as well:

GH issues and GH discussions

Hi, This has been already discussed in the past. But due to recent changes in ASF Jira infrastructure (limitation of Jira users, validation of account creation). Maybe we could reconsider moving from Jira to GH issues and why not simplify the workflow as well. I imagine not having to create an