[GitHub] [maven-shade-plugin] dependabot[bot] opened a new pull request #99: Bump jdependency from 2.6.0 to 2.7.0

dependabot[bot] opened a new pull request #99: URL: https://github.com/apache/maven-shade-plugin/pull/99 Bumps [jdependency](https://github.com/tcurdt/jdependency) from 2.6.0 to 2.7.0. Changelog Sourced from https://github.com/tcurdt/jdependency/blob/master/HISTORY.md";>jdependenc

[jira] [Commented] (SUREFIRE-1916) thread blocked freezing progress

[ https://issues.apache.org/jira/browse/SUREFIRE-1916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17356094#comment-17356094 ] Peter Firmstone commented on SUREFIRE-1916: --- Some more info after killing pr

[jira] [Created] (SUREFIRE-1916) thread blocked freezing progress

Peter Firmstone created SUREFIRE-1916: - Summary: thread blocked freezing progress Key: SUREFIRE-1916 URL: https://issues.apache.org/jira/browse/SUREFIRE-1916 Project: Maven Surefire Issue

[GitHub] [maven-apache-parent] michael-o commented on pull request #40: MPOM-244 upload SHA-512 only for source-release to staging repo

michael-o commented on pull request #40: URL: https://github.com/apache/maven-apache-parent/pull/40#issuecomment-853395638 > changed pom.xml version to 23 and ran the same `mvn -Papache-release deploy -Daether.checksums.algorithms="SHA-512,SHA-1,MD5"` > => perfect staging repository: h

[jira] [Commented] (MSHADE-395) 3.3.0-SNAPSHOT not available in repository

[ https://issues.apache.org/jira/browse/MSHADE-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17355959#comment-17355959 ] Michael Osipov commented on MSHADE-395: --- No one will make such guarantees. > 3.3.0

[jira] [Assigned] (MSHARED-546) Change groupId from org.apache.maven to org.apache.maven.shared

[ https://issues.apache.org/jira/browse/MSHARED-546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz reassigned MSHARED-546: Assignee: Sylwester Lachiewicz > Change groupId from org.apache.maven to

[jira] [Updated] (MSHARED-955) Make MavenArchiver.parseOutputTimestamp static

[ https://issues.apache.org/jira/browse/MSHARED-955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MSHARED-955: - Fix Version/s: maven-archiver-3.5.2 > Make MavenArchiver.parseOutputTimestamp st

[jira] [Updated] (MSHARED-991) Require Java 8

[ https://issues.apache.org/jira/browse/MSHARED-991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MSHARED-991: - Fix Version/s: maven-archiver-3.5.2 > Require Java 8 > -- > >

[jira] [Updated] (MSHARED-991) Require Java 8

[ https://issues.apache.org/jira/browse/MSHARED-991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MSHARED-991: - Component/s: maven-archiver > Require Java 8 > -- > >

[jira] [Commented] (MSHADE-395) 3.3.0-SNAPSHOT not available in repository

[ https://issues.apache.org/jira/browse/MSHADE-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17355956#comment-17355956 ] Gabriel Wolf commented on MSHADE-395: - I have no problem, that i use a snapshot. Anyw

[jira] [Updated] (MSHARED-546) Change groupId from org.apache.maven to org.apache.maven.shared

[ https://issues.apache.org/jira/browse/MSHARED-546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MSHARED-546: - Fix Version/s: maven-archiver-3.5.2 > Change groupId from org.apache.maven to or

[jira] [Created] (MSHARED-991) Require Java 8

Sylwester Lachiewicz created MSHARED-991: Summary: Require Java 8 Key: MSHARED-991 URL: https://issues.apache.org/jira/browse/MSHARED-991 Project: Maven Shared Components Issue Type:

[GitHub] [maven-apache-parent] hboutemy commented on pull request #40: MPOM-244 upload SHA-512 only for source-release to staging repo

hboutemy commented on pull request #40: URL: https://github.com/apache/maven-apache-parent/pull/40#issuecomment-853358621 changed pom.xml version to 23 and ran the same `mvn -Papache-release deploy -Daether.checksums.algorithms="SHA-512,SHA-1,MD5"` => perfect staging repository: https:

[GitHub] [maven-apache-parent] hboutemy commented on pull request #40: MPOM-244 upload SHA-512 only for source-release to staging repo

hboutemy commented on pull request #40: URL: https://github.com/apache/maven-apache-parent/pull/40#issuecomment-853356689 oh nice, I didn't know that content! I ran `mvn -Papache-release deploy -Daether.checksums.algorithms="SHA-512,SHA-1,MD5"` and got id 86 of https://repository.apach

[GitHub] [maven-apache-parent] michael-o commented on pull request #40: MPOM-244 upload SHA-512 only for source-release to staging repo

michael-o commented on pull request #40: URL: https://github.com/apache/maven-apache-parent/pull/40#issuecomment-853342953 > > > > People can already configure it. I just want to avoid surprises for all Apache folks. E.g., Mark Thomas does this actively now. > > can you show

[GitHub] [maven-apache-parent] michael-o commented on pull request #40: MPOM-244 upload SHA-512 only for source-release to staging repo

michael-o commented on pull request #40: URL: https://github.com/apache/maven-apache-parent/pull/40#issuecomment-853342182 > > > FYI, I added some instructions to calculate sha512 in dist: [apache/maven-site@29bc21e](https://github.com/apache/maven-site/commit/29bc21e3dc9d2bb7ff61c

[GitHub] [maven-apache-parent] hboutemy commented on pull request #40: MPOM-244 upload SHA-512 only for source-release to staging repo

hboutemy commented on pull request #40: URL: https://github.com/apache/maven-apache-parent/pull/40#issuecomment-853339600 > People can already configure it. I just want to avoid surprises for all Apache folks. E.g., Mark Thomas does this actively now. can you show me, please? I don'

[GitHub] [maven-apache-parent] hboutemy commented on pull request #40: MPOM-244 upload SHA-512 only for source-release to staging repo

hboutemy commented on pull request #40: URL: https://github.com/apache/maven-apache-parent/pull/40#issuecomment-853338590 FYI, I added some instructions to calculate sha512 in dist: https://github.com/apache/maven-site/commit/29bc21e3dc9d2bb7ff61ce49cecf8a8600b9b5d1 and while at it, I r

[GitHub] [maven-apache-parent] michael-o commented on pull request #40: MPOM-244 upload SHA-512 only for source-release to staging repo

michael-o commented on pull request #40: URL: https://github.com/apache/maven-apache-parent/pull/40#issuecomment-853336228 See here: https://repo1.maven.org/maven2/org/apache/tomcat/tomcat-catalina/10.0.6/ Produced by Resoler via Ant. -- This is an automated message from the Apac

[GitHub] [maven-apache-parent] michael-o commented on pull request #40: MPOM-244 upload SHA-512 only for source-release to staging repo

michael-o commented on pull request #40: URL: https://github.com/apache/maven-apache-parent/pull/40#issuecomment-853335882 > > > the day Maven Resolver will be configured to upload sha512, we'll remove this hack (because, yes, it's a hack to ease our release process) > When do y

[GitHub] [maven-apache-parent] hboutemy commented on pull request #40: MPOM-244 upload SHA-512 only for source-release to staging repo

hboutemy commented on pull request #40: URL: https://github.com/apache/maven-apache-parent/pull/40#issuecomment-853335146 the day Maven Resolver will be configured to upload sha512, we'll remove this hack (because, yes, it's a hack to ease our release process) When do you expect Maven R

[GitHub] [maven-apache-parent] michael-o commented on pull request #40: MPOM-244 upload SHA-512 only for source-release to staging repo

michael-o commented on pull request #40: URL: https://github.com/apache/maven-apache-parent/pull/40#issuecomment-853328882 @hboutemy I wonder what will happen during a release: Maven Resolver uploads SHA-512, this change uploads it. Will Nexus staging reject it? This should be tested befo

[GitHub] [maven-apache-parent] hboutemy edited a comment on pull request #40: MPOM-244 upload SHA-512 only for source-release to staging repo

hboutemy edited a comment on pull request #40: URL: https://github.com/apache/maven-apache-parent/pull/40#issuecomment-853323824 FYI, I tried `mvn -Papache-release deploy` with the sha512 attachments and got https://repository.apache.org/content/repositories/snapshots/org/apache/apache/24

[GitHub] [maven-apache-parent] hboutemy commented on pull request #40: MPOM-244 upload SHA-512 only for source-release to staging repo

hboutemy commented on pull request #40: URL: https://github.com/apache/maven-apache-parent/pull/40#issuecomment-853323824 FYI, I tried `mvn -Papache-release deploy` with the sha512 attachments and got https://repository.apache.org/content/repositories/snapshots/org/apache/apache/24-SNAPSH

[GitHub] [maven-doxia-linkcheck] michael-o commented on pull request #7: remove dependency on Modello

michael-o commented on pull request #7: URL: https://github.com/apache/maven-doxia-linkcheck/pull/7#issuecomment-853322238 I don't understand who those two issues are related to Modello. For me, Modello works in Eclipse. I am against adding generated code. I would prefer to retire this co

[jira] [Closed] (MDEP-747) analyze-only failed: Unsupported class file major version 61 (Java 17)

[ https://issues.apache.org/jira/browse/MDEP-747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MDEP-747. -- Resolution: Fixed thanks for the followup, [~namannigam12] > analyze-only failed: Unsupported class file

[jira] [Comment Edited] (MSHADE-395) 3.3.0-SNAPSHOT not available in repository

[ https://issues.apache.org/jira/browse/MSHADE-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17355865#comment-17355865 ] Michael Osipov edited comment on MSHADE-395 at 6/2/21, 5:06 PM: ---

[jira] [Commented] (MSHADE-395) 3.3.0-SNAPSHOT not available in repository

[ https://issues.apache.org/jira/browse/MSHADE-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17355865#comment-17355865 ] Michael Osipov commented on MSHADE-395: --- 11th commandment: One shall not rely on sn

[GitHub] [maven-shared-utils] elharo opened a new pull request #92: fix double typo

elharo opened a new pull request #92: URL: https://github.com/apache/maven-shared-utils/pull/92 @slachiewicz -- 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. For queries a

[GitHub] [maven-shared-utils] kwin commented on a change in pull request #54: rework directory scanner to ensure it can enforce exclusions and it uses path

kwin commented on a change in pull request #54: URL: https://github.com/apache/maven-shared-utils/pull/54#discussion_r644008249 ## File path: src/main/java/org/apache/maven/shared/utils/io/conductor/EnforceExcludesOverIncludes.java ## @@ -0,0 +1,58 @@ +package org.apache.maven

[jira] [Updated] (MCHANGES-399) change report: add further column: date

[ https://issues.apache.org/jira/browse/MCHANGES-399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MCHANGES-399: Fix Version/s: waiting-for-feedback > change report: add further column: date >

[jira] [Commented] (MSHARED-989) Undeprecate DirectoryScanner and MatchPattern(s)

[ https://issues.apache.org/jira/browse/MSHARED-989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17355768#comment-17355768 ] Romain Manni-Bucau commented on MSHARED-989: [~kwin] IIRC it was the idea ye

[GitHub] [maven-shared-utils] kwin commented on a change in pull request #54: rework directory scanner to ensure it can enforce exclusions and it uses path

kwin commented on a change in pull request #54: URL: https://github.com/apache/maven-shared-utils/pull/54#discussion_r644008249 ## File path: src/main/java/org/apache/maven/shared/utils/io/conductor/EnforceExcludesOverIncludes.java ## @@ -0,0 +1,58 @@ +package org.apache.maven

[GitHub] [maven-shared-utils] kwin commented on pull request #54: rework directory scanner to ensure it can enforce exclusions and it uses path

kwin commented on pull request #54: URL: https://github.com/apache/maven-shared-utils/pull/54#issuecomment-853062525 IMHO this is relevant and would fix https://issues.apache.org/jira/browse/MSHARED-989. -- This is an automated message from the Apache Git Service. To respond to the messa

[jira] [Commented] (MSHARED-989) Undeprecate DirectoryScanner and MatchPattern(s)

[ https://issues.apache.org/jira/browse/MSHARED-989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17355754#comment-17355754 ] Konrad Windszus commented on MSHARED-989: - I think this is mostly already provid

[jira] [Commented] (MCHANGES-399) change report: add further column: date

[ https://issues.apache.org/jira/browse/MCHANGES-399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17355726#comment-17355726 ] Michael Osipov commented on MCHANGES-399: - Did you check https://maven.apache.

[jira] [Updated] (MSHADE-395) 3.3.0-SNAPSHOT not available in repository

[ https://issues.apache.org/jira/browse/MSHADE-395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabriel Wolf updated MSHADE-395: Description: Hey, i am one of the developers from BetonQuest [https://github.com/BetonQuest/BetonQ

[jira] [Commented] (MCHANGES-374) Allow OAuth authentication in Jira

[ https://issues.apache.org/jira/browse/MCHANGES-374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17355719#comment-17355719 ] Michael Osipov commented on MCHANGES-374: - OAuth isn't authentication. > Allow

[jira] [Created] (MSHADE-395) 3.3.0-SNAPSHOT not available in repository

Gabriel Wolf created MSHADE-395: --- Summary: 3.3.0-SNAPSHOT not available in repository Key: MSHADE-395 URL: https://issues.apache.org/jira/browse/MSHADE-395 Project: Maven Shade Plugin Issue Typ

[GitHub] [maven-dependency-plugin] van-vliet commented on pull request #133: [MDEP-739] Dependency Plugin go-offline doesn't respect artifact classifier

van-vliet commented on pull request #133: URL: https://github.com/apache/maven-dependency-plugin/pull/133#issuecomment-852882664 @michael-o I am not sure how to describe the cruciality to you. I can describe the impact of not seeing this change released: My colleagues and I have a c

[GitHub] [maven] gnodet commented on pull request #413: [MNG-6843] Thread-safe artifacts in MavenProject

gnodet commented on pull request #413: URL: https://github.com/apache/maven/pull/413#issuecomment-852829527 @Tibor17 See https://github.com/apache/maven/pull/475 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL

[GitHub] [maven] gnodet commented on pull request #476: [MNG-7156] Parallel build can cause issues between clean and forked g…

gnodet commented on pull request #476: URL: https://github.com/apache/maven/pull/476#issuecomment-852804630 > Will this also resolve `-DdeployAtEnd=true`? I don't understand. This only adds a locking mechanism to avoid conflicts caused by parallel execution between the normal lifecy

[jira] [Commented] (MDEP-568) dependency:go-offline -DexcludeGroupIds=xxxx still try to resolve artifacts in the excluded group xxxx

[ https://issues.apache.org/jira/browse/MDEP-568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17355526#comment-17355526 ] Hudson commented on MDEP-568: - Build succeeded in Jenkins: Maven » Maven TLP » maven-dependency